Last scanned:
This base/runtime image is a clean foundation for building production images. It is an official Docker Hub image pinned by digest, and INPUT 3 reports 0 exposed vulnerabilities with a maximum exposed severity of 0.0. The 278 post-exploit-only findings have a maximum severity of 4.5 and none at 6.0 or higher; examples include CVE-2026-18798 and CVE-2024-52005. These findings are not on the exposed attack surface, so they do not change the SAFE verdict for images built on this base. 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-18798 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | MEDIUM4.08 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | dirmngr 2.4.7-21+deb13u1+b4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg 2.4.7-21+deb13u1+b4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg-agent 2.4.7-21+deb13u1+b4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgconf 2.4.7-21+deb13u1+b4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgsm 2.4.7-21+deb13u1+b4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-106583 | LOW3.98 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-106553 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106555 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW3.77 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53612 | LOW3.57 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW3.57 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW3.57 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW3.57 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW3.57 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW3.57 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63073 | LOW3.54 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-90803 | LOW3.47 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-106552 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-106585 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.25.0-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-16599 | LOW3.31 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 13.7% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54872 | LOW3.01 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW3.01 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.01 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.01 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-60002 | LOW2.87 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73282 | LOW2.86 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2019-6110 | LOW2.81 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 24.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.8 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73283 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-24975 | LOW2.7 | git 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | LOW2.7 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.7 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | LOW2.7 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | LOW2.7 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.8-2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42772 | LOW2.7 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW2.7 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW2.7 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW2.7 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-84784 | LOW2.7 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-92386 | LOW2.58 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.55 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.55 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54875 | LOW2.4 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107929 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-87863 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-92387 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-106586 | LOW2.19 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 8.14.1-2+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80229 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-106582 | LOW1.89 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55654 | LOW1.89 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-35189 | LOW1.89 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW1.89 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW1.89 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | dirmngr 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpg 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpg-agent 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpgconf 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW1.84 | gpgsm 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73281 | LOW1.78 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.4.7-21+deb13u1+b4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.4.7-21+deb13u1+b4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.4.7-21+deb13u1+b4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+deb13u1+b4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.4.7-21+deb13u1+b4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-106584 | LOW1.68 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-106587 | LOW1.68 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-29 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | dirmngr 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-agent 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgconf 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgsm 2.4.7-21+deb13u1+b4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-34152 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-42217 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-42217 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-20884 | NONE0 | libraw23t64 0.21.4-2 fixed in 0.21.4-2+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-24450 | NONE0 | libraw23t64 0.21.4-2 fixed in 0.21.4-2+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-24660 | NONE0 | libraw23t64 0.21.4-2 fixed in 0.21.4-2+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-81642 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-82717 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49261 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-8376 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-50252 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2026-58016 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-42216 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-42216 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44172 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-13221 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32740 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-97380 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97380 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97380 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-41142 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-41142 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2016-9580 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9581 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-16376 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2016-9580 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9581 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-16376 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-14662 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-14664 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14669 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-14670 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14671 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14677 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14680 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16239 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-19385 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6473 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-14662 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-14664 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14669 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-14670 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14671 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14677 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14680 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16239 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-19385 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6473 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-16742 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64562 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68156 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68159 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74588 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74597 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74669 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74705 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74744 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89656 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89674 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89676 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89495 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97380 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74580 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-44690 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80725 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74860 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74860 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107818 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107818 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107818 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18408 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-18408 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107818 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88807 | NONE0 | libxrender-dev 1:0.9.12-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-88807 | NONE0 | libxrender1 1:0.9.12-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-80586 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-77214 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-77214 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-34191 | NONE0 | libaprutil1t64 1.6.3-3+b1 fixed in 1.6.3-3+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-92392 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-92392 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-92392 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-14668 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6464 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14668 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6464 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19445 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19445 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68376 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89526 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89653 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90011 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-93787 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19445 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19445 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15741 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-15741 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89524 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-96889 | NONE0 | gir1.2-rsvg-2.0 2.60.0+dfsg-1 fixed in 2.60.0+dfsg-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-24882 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1365 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1372 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-76957 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76957 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12495 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12839 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12840 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27622 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34588 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-12495 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12839 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12840 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27622 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34588 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89161 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-96889 | NONE0 | librsvg2-2 2.60.0+dfsg-1 fixed in 2.60.0+dfsg-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-96889 | NONE0 | librsvg2-common 2.60.0+dfsg-1 fixed in 2.60.0+dfsg-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-96889 | NONE0 | librsvg2-dev 2.60.0+dfsg-1 fixed in 2.60.0+dfsg-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86138 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86139 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86140 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86142 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86144 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86138 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86139 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86140 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86142 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86144 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64564 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-64565 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68143 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68200 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68264 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68290 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68398 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74581 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74582 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74583 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74746 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74753 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80522 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80714 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80951 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81000 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89465 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89508 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89617 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89725 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89736 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89761 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89970 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-93288 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93817 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93827 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97528 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97602 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98116 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98524 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | cpp-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | cpp-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | g++-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | g++-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | gcc-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | gcc-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libasan8 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libatomic1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libcc1-0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libgcc-14-dev 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libgomp1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libhwasan0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libitm1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | liblsan0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86047 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86047 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86047 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libquadmath0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libstdc++-14-dev 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libtsan2 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | libubsan1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-86047 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-103111 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-61857 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-34501 | NONE0 | libaprutil1t64 1.6.3-3+b1 fixed in 1.6.3-3+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34502 | NONE0 | libaprutil1t64 1.6.3-3+b1 fixed in 1.6.3-3+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libbinutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libctf0 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9545 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9545 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-9545 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33164 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1352 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-66046 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-76956 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93990 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66046 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-76956 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93990 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-6829 | NONE0 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-58011 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-61863 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61866 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86420 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-86421 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93589 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93590 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107815 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-107815 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-107815 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-64181 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34543 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-64181 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34543 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-9113 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9114 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9113 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9114 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15742 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15742 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-20889 | NONE0 | libraw23t64 0.21.4-2 fixed in 0.21.4-2+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-21413 | NONE0 | libraw23t64 0.21.4-2 fixed in 0.21.4-2+deb13u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-66864 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58050 | NONE0 | libssh2-1-dev 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58050 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-14456 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-18798 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-63072 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-63076 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-14457 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-54874 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63074 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63075 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-14456 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-18798 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-63072 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-63076 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-14457 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-54874 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63074 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63075 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-32665 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40622 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40691 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-55973 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80225 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81634 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-85501 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-88806 | NONE0 | libx11-6 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88806 | NONE0 | libx11-data 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88806 | NONE0 | libx11-dev 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97417 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98442 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98532 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98548 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98550 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98573 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-74586 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-107815 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-14456 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-18798 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-63072 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-63076 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-14457 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-54874 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63074 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63075 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15308 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7210 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89157 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19553 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19553 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-84782 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-84782 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74631 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89783 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-84782 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19553 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19553 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9080 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9080 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-9080 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34544 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34545 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-34544 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34545 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-52490 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52491 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52492 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52490 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52491 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52492 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52490 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52491 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52492 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86143 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86143 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68121 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68166 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68201 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68294 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74574 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93262 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93813 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97415 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97505 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-107823 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-107823 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-107823 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-6471 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6471 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-107823 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-48165 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68431 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32741 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32882 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34379 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40244 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40250 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59184 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59186 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59187 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59189 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59981 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59982 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68515 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34379 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40244 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40250 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59184 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59186 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59187 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-59189 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59981 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-59982 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68515 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-14679 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-14679 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-82049 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82049 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80530 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89481 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89846 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98155 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64572 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68099 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68155 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68188 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68263 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68373 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89596 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89700 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89779 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93812 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97425 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97494 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97495 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97497 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2026-82049 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82049 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15366 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15367 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | cpp-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | cpp-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | g++-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | g++-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | gcc-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | gcc-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libasan8 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libatomic1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libcc1-0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libgcc-14-dev 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libgomp1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libhwasan0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libitm1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | liblsan0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109964 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libquadmath0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libstdc++-14-dev 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libtsan2 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102010 | NONE0 | libubsan1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68123 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68140 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68144 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68145 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68160 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68335 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68432 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72137 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72463 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74503 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74520 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74615 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74616 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74630 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74743 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80780 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80849 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80850 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80878 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80887 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80921 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81003 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89479 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89487 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89488 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89530 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89536 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89545 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89563 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89564 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89569 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89607 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89652 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89659 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89663 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89669 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89690 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89708 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89713 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89777 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89894 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89932 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90036 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90049 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90227 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98378 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64216 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64573 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64577 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68117 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68125 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68128 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68131 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68142 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68147 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68148 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68149 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68154 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68157 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68158 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68181 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68266 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68267 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68276 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68300 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-68315 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68320 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68325 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68338 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68349 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68351 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68363 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68365 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68368 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68377 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68381 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68388 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68389 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68393 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68397 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68402 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68442 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72046 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72111 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72125 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72500 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74440 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74447 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74452 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74501 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74513 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74517 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74535 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74541 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74587 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74594 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74598 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74608 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74609 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74610 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74612 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74614 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74621 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74624 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74637 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74641 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74656 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74660 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74661 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74666 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74668 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74672 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74677 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74682 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74684 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74688 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74692 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74700 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74714 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74724 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74730 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74737 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80528 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80540 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80552 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80553 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80558 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80561 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80584 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80585 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80589 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80681 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80691 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80700 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80702 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80710 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80716 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80718 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80722 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80944 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80945 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80947 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80952 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80971 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80973 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80976 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80977 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80978 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80979 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80982 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80989 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80994 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81001 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81002 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-81008 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89440 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89444 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89445 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89448 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89456 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89458 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89476 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89477 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89478 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89480 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89482 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89485 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89500 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89501 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89510 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89532 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89533 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89534 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89535 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89538 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89540 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89541 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89542 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89543 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89547 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89548 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89550 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89551 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89553 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89555 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89558 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89559 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89560 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89575 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89580 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89581 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89582 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89583 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89587 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89602 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89606 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89609 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89625 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89634 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89636 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89643 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89649 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89650 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89651 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89655 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89657 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89658 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89660 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89662 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89665 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89666 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89671 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89672 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89680 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89683 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89684 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89685 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89686 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89688 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89691 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89693 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89694 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89697 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89698 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89702 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89703 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89704 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89706 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89707 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89712 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89719 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89729 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89741 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89746 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89747 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89755 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89766 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89930 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90071 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90092 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90102 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90110 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90128 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90135 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90142 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90151 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90177 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90180 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90185 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90189 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90201 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90203 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90207 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90230 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90235 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90240 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90241 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90243 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90256 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90260 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90284 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90292 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90294 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90303 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90307 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90313 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90317 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90325 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90334 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90427 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93189 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93207 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93283 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93800 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97427 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97429 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97476 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97496 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97524 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97527 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97547 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97555 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97557 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97564 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97573 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97575 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97583 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97584 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97595 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97608 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97611 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97612 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97620 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97926 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97931 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97934 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97936 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97940 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97954 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97957 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97965 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97986 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97990 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97991 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98014 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98015 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98016 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98023 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98025 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98032 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98037 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98041 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98047 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98048 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98066 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98068 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98069 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98070 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98075 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98108 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98122 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98123 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98130 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98154 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98184 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98211 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98214 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98215 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98216 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98230 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98231 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98238 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98239 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98246 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98247 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98249 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98261 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98291 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98296 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98366 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98368 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98376 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98382 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98392 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98401 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98429 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53612 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53614 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86410 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86410 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86410 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-90803 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90414 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107821 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-107821 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-107821 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68284 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89579 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98590 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98591 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98599 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93144 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107821 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-60585 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-60585 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-60585 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89640 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90255 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-60585 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-107778 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2-dev 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libctf0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-19931 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-92388 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86414 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92390 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-19931 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-92388 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86414 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92390 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-19931 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-92388 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86414 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92390 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-dev 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 fixed in 2.1.13-stable-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libgprofng0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49271 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49271 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49271 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-9937 | NONE0 | libjbig-dev 2.1-6.1+b2 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-9937 | NONE0 | libjbig0 2.1-6.1+b2 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-107778 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107778 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-53532 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54920 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68516 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53532 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54920 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68516 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-39329 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-10505 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9115 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9116 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-9117 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-6988 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-39329 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-10505 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9115 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9116 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-9117 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2019-6988 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-89158 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89158 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89158 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89158 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89158 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89160 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37769 | NONE0 | libpixman-1-0 0.44.0-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-37769 | NONE0 | libpixman-1-dev 0.44.0-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-14663 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-14663 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-58051 | NONE0 | libssh2-1-dev 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66032 | NONE0 | libssh2-1-dev 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66033 | NONE0 | libssh2-1-dev 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58051 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66032 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66033 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-50248 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11-6 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11-data 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94283 | NONE0 | libx11-dev 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89511 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89696 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98452 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98454 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98457 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98526 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98578 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98582 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98597 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98600 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98702 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-11972 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-107822 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-60331 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107822 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-60331 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107822 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-60331 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53092 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72183 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98039 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107822 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-60331 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-12345 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-12345 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89965 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-12345 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-12345 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32327 | NONE0 | libaprutil1t64 1.6.3-3+b1 fixed in 1.6.3-3+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72522 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.8.3-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72522 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.8.3-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-60747 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-60747 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-60747 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55373 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55373 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | libp11-kit-dev 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18938 | NONE0 | libp11-kit-dev 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18938 | NONE0 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98545 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98575 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-60747 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18090 | NONE0 | gir1.2-gdkpixbuf-2.0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18090 | NONE0 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18090 | NONE0 | libgdk-pixbuf-2.0-dev 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18090 | NONE0 | libgdk-pixbuf2.0-bin 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18090 | NONE0 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18495 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18495 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18495 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86137 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86137 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68350 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89786 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90054 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90068 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89778 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90211 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-106565 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-49506 | NONE0 | libaprutil1t64 1.6.3-3+b1 fixed in 1.6.3-3+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102633 | NONE0 | libexpat1 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-102633 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2236 | NONE0 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-1153 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106565 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106567 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89156 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46675 | NONE0 | libpng-dev 1.6.48-1+deb13u5 fixed in 1.6.48-1+deb13u6 | — | Not Applicable |
| CVE-2026-46675 | NONE0 | libpng16-16t64 1.6.48-1+deb13u5 fixed in 1.6.48-1+deb13u6 | — | Not Applicable |
| CVE-2025-1153 | NONE0 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-66034 | NONE0 | libssh2-1-dev 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66034 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54872 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72897 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75805 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77696 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63073 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-54872 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72897 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75805 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77696 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63073 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-14586 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44621 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52863 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-55717 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55990 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55991 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78227 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-82720 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98561 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98586 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-54872 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72897 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75805 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77696 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63073 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-93101 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-87910 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-87910 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-87910 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-87910 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98440 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98464 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86423 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2017-13716 | NONE0 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2-dev 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1371 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1377 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1 2.8.2-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1-dev 2.8.2-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95512 | NONE0 | libfreetype-dev 2.13.3+dfsg-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95512 | NONE0 | libfreetype6 2.13.3+dfsg-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-86423 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86425 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-48074 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-55059 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55371 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59183 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59983 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59984 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59985 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61555 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88384 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-48074 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-55059 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55371 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59183 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59983 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59984 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59985 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61555 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88384 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39328 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39328 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-24890 | NONE0 | libraw23t64 0.21.4-2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-88387 | NONE0 | libraw23t64 0.21.4-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11-6 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11-data 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94284 | NONE0 | libx11-dev 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76781 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76781 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-10911 | NONE0 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-10911 | NONE0 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21817 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38525 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100070 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100074 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100075 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100078 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100079 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23143 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64058 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64205 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64290 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64567 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64569 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64570 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64571 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64574 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64576 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64578 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64579 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68104 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68106 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68107 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68111 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68116 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68119 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68126 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68127 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68129 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68135 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68137 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68139 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68141 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68153 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68178 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68180 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68182 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68183 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68184 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68186 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68187 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68189 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68190 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68193 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68194 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68195 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68196 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68197 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68204 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68209 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68212 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68214 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68215 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68219 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68222 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68228 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68229 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68231 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68243 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68244 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68248 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68260 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68261 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68262 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68269 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68271 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68272 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68295 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68296 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68297 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68299 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68306 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68307 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68308 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68309 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68310 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68311 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68317 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68318 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68319 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68321 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68324 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68326 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68339 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68344 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68348 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68352 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68353 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68354 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68355 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68357 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68358 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68360 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68362 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68366 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68369 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68371 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68372 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68385 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68392 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68394 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68395 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68410 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68411 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68413 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68414 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68416 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68417 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68419 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68421 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68425 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68428 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68433 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68437 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68443 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68444 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68446 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72030 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72101 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72103 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72113 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72114 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72115 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72116 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72119 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72121 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72124 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72146 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72175 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72244 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72355 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72365 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72367 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72372 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72388 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74258 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74354 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74442 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74451 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74500 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74504 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74524 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74529 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74531 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74532 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74542 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74572 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74576 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74585 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74589 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74590 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74592 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74595 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74599 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74602 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74603 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74606 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74607 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74613 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74618 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74619 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74620 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74625 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74628 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74632 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74634 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74635 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74646 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74647 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74648 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74649 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74650 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74651 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74655 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74657 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74658 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74659 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74665 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74667 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74670 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74671 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74673 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74675 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74679 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74683 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74685 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74689 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74693 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74694 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74696 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74701 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74704 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74710 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74712 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74719 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74720 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74725 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74726 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74736 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74739 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74740 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74742 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74748 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80526 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80527 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80529 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80539 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80541 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80547 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80548 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80550 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80551 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80554 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80556 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80559 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80560 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80563 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80565 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80566 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80567 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80568 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80569 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80570 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80573 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80574 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80575 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80576 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80578 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80587 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80614 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80655 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80678 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80680 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80684 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80686 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80694 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80695 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80696 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80703 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80706 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80707 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80708 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80709 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80711 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80717 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80723 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80902 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80903 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80928 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80931 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80932 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80933 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80935 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80938 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80942 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80943 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80964 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80965 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80966 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80968 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80969 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80972 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80984 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80991 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80992 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80999 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81011 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81012 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81013 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81014 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81017 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89438 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89442 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89443 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89451 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89455 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89457 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89461 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89462 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89463 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89464 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89466 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89467 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89468 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89469 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89470 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89471 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89472 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89473 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89474 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89475 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89483 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89489 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89490 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89491 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89492 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89493 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89494 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89496 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89497 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89498 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89503 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89504 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89512 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89515 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89525 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89544 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89549 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89554 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89557 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89561 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89565 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89567 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89572 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89573 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89574 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89585 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89588 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89589 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89594 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89595 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89597 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89599 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89608 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89615 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89616 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89621 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89622 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89624 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89626 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89628 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89639 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89699 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89711 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89718 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89720 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89723 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89724 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89726 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89730 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89731 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89732 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89733 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89735 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89738 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89740 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89742 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89743 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89750 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89751 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89756 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89762 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89763 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89768 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89771 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89824 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89881 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89896 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89909 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90007 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90015 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90021 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90056 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90063 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90073 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90074 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90075 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90076 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90081 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90088 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90090 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90091 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90101 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90103 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90107 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90108 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90112 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90114 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90115 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90122 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90124 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90137 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90140 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90141 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90143 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90148 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90150 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90152 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90157 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90158 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90159 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90165 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90166 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90170 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90175 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90176 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90192 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90193 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90195 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90196 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90198 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90199 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90200 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90214 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90217 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90218 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90219 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90220 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90221 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90222 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90223 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90224 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90225 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90226 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90228 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90229 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90231 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90245 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90248 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90249 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90251 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90257 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90274 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90279 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90282 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90286 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90287 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90291 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90293 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90295 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90296 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90297 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90298 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90302 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90308 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90309 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90314 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90316 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90318 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90319 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90322 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90324 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90327 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90341 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90344 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90348 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90352 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90354 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90361 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90362 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90364 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90378 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90404 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90407 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90422 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90434 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92488 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92504 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92519 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93056 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93071 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93089 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93090 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93151 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-93159 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93185 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93188 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93190 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93191 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93192 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93203 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93204 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93228 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93261 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93264 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93270 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93271 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93276 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93278 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93279 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93280 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93281 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93287 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93782 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93786 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93789 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93790 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93791 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93793 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93796 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93799 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93802 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93803 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93804 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93805 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93806 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93807 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93808 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93815 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93816 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93818 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93819 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93820 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93821 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93822 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93824 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93826 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93830 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97407 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97408 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97409 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97410 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97411 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97412 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97413 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97414 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97418 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97419 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97420 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97421 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97428 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97434 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97435 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97437 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97438 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97439 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97442 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97444 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97448 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97451 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97455 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97456 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97472 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97475 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97482 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97485 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97486 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97489 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97490 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97500 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97502 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97504 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97506 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97507 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97508 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97512 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97514 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97517 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97518 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97523 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97526 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97538 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97539 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97540 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97541 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97545 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97551 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97560 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97562 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97571 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97572 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97574 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97576 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97577 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97578 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97579 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97581 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97582 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97587 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97596 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97598 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97599 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97600 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97603 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97604 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97617 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97908 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97909 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97910 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97915 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97916 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97917 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97919 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97920 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97924 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97925 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97929 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97930 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97945 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97951 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97952 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97953 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97960 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97961 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97962 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97964 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97966 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97967 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97968 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97969 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97970 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97973 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97976 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97977 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97978 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97981 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97982 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97987 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97992 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97994 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97995 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97996 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97998 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98001 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98006 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98008 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98013 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98017 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98018 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98020 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98022 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98024 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98026 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98027 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98028 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98029 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98030 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98031 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98049 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98051 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98052 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98053 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98054 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98056 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98057 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98062 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98063 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98071 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98072 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98080 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98082 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98092 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98103 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98104 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98105 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98107 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98111 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98113 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98114 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98115 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98118 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98121 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98134 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98142 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98151 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98152 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98157 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98158 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98159 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98160 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98164 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98168 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98200 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98206 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98218 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98228 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98267 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98277 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98293 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98336 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98360 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98384 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98408 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98410 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98455 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98459 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98461 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98462 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98477 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98503 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98511 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98512 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98517 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98521 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98522 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98539 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98541 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98547 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98554 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98566 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98567 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98580 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98596 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98801 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-100071 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68110 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68115 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68133 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68164 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68165 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68175 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68176 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68216 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68217 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68218 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68226 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68227 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68234 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68249 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68250 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68256 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68281 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68301 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68304 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68313 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68328 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68331 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68333 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68336 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68346 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68375 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68403 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68405 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68406 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68407 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68422 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68429 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68430 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68434 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68439 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68450 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72032 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72040 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72117 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72118 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72366 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72485 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72496 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72497 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74448 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74483 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74601 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74622 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74623 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74636 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74644 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74654 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74663 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74664 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74676 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74678 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74680 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74717 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74718 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74722 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74728 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80525 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80532 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80533 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80535 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80549 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80577 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80679 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80689 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80704 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80705 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80715 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80727 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80784 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80930 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80939 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80940 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80941 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80949 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80963 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80967 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80974 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80983 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80987 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80988 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80990 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80996 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80997 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89439 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89453 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89454 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89484 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89502 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89531 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89539 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89552 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89566 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89576 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89586 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89593 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89598 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89604 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89605 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89618 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89627 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89644 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89645 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89647 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89667 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89710 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89717 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89744 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89749 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89752 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89753 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89759 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89765 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89816 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89872 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89877 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89886 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89900 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89923 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89924 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89925 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89944 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89953 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89975 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89982 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90053 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90055 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90058 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90060 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90062 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90065 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90066 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90067 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90070 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90072 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90078 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90085 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90109 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90119 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90125 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90126 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90130 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90138 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90139 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90144 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90147 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90160 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90178 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90184 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90186 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90187 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90188 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90190 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90194 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90202 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90209 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90213 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90215 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90216 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90250 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90253 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90254 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90261 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90275 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90280 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90281 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90283 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90285 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90290 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90306 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90390 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90402 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90411 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90415 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90424 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92494 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92524 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93072 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93082 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93083 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93102 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93126 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93130 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93136 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93145 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93161 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93186 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93268 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93269 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93273 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93274 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93286 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93785 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93788 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93794 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93795 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93798 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93801 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93811 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93814 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93823 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93825 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93828 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93829 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97416 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97430 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97436 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97440 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97441 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97443 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97446 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97473 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97481 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97483 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97484 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97487 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97488 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97491 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97492 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97509 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97510 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97516 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97521 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97522 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97542 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97543 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97544 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97546 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97549 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97552 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97556 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97592 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97601 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97606 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97607 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97613 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97616 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97899 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97900 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97902 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97904 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97905 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97907 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97921 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97922 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97923 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97927 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97928 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97948 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97958 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97959 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97963 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97979 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97984 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97985 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97993 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98007 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98009 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98010 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98011 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98012 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98021 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98038 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98045 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98046 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98055 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98059 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98064 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98074 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98110 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98119 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98126 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98127 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98128 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98129 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98147 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98235 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98263 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98270 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98297 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98346 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98387 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98388 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98394 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98398 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98399 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98400 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98402 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98404 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98431 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0864 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107816 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85985 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107816 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85985 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107816 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85985 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-dev 1.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90086 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107816 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85985 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-16768 | NONE0 | gir1.2-gdkpixbuf-2.0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | girepository-tools 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-8674 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-8674 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-8674 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-86409 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86409 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-86409 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-16768 | NONE0 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16768 | NONE0 | libgdk-pixbuf-2.0-dev 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16768 | NONE0 | libgdk-pixbuf2.0-bin 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16768 | NONE0 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-86469 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-102635 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106564 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106568 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106577 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109259 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109262 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109265 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109269 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109276 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64685 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34380 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34380 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-14672 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-14672 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5342 | NONE0 | libraw23t64 0.21.4-2 fixed in 0.21.4-2+deb13u1 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66035 | NONE0 | libssh2-1-dev 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-66035 | NONE0 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42772 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54873 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75804 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75806 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-84784 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42772 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54873 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75804 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75806 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-84784 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50045 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-50251 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2015-9019 | NONE0 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2015-9019 | NONE0 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98465 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98576 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98577 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42772 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54873 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75804 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75806 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-84784 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-12781 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4360 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74502 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11-6 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11-data 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-94285 | NONE0 | libx11-dev 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98475 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98501 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-1.0 1.0.8-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-dev 1.0.8-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-bin 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-bin 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-33165 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-1176 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-62363 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-34589 | NONE0 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34589 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-107708 | NONE0 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47023 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47023 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47023 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47023 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107928 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82208 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107928 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82208 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107928 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82208 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109275 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56416 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98549 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-81893 | NONE0 | gir1.2-gdkpixbuf-2.0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-1376 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81893 | NONE0 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81893 | NONE0 | libgdk-pixbuf-2.0-dev 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81893 | NONE0 | libgdk-pixbuf2.0-bin 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81893 | NONE0 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-14159 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-14159 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62343 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-62946 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54875 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54875 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98109 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98301 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98441 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98444 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98476 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98507 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98508 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98510 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98515 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98523 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98536 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98537 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98538 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98546 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98555 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98559 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98568 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98581 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98662 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98749 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98768 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98826 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80534 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90262 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54875 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | uuid-dev 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98711 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109281 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107817 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-60184 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107817 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-60184 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-107817 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-60184 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-77955 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80531 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98078 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98435 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98443 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98460 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98525 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98534 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98565 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98569 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98572 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98583 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89460 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-107817 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-60184 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-92386 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92386 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92386 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93588 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85745 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85745 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85745 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-39327 | NONE0 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-39327 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-14678 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18024 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6470 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-14678 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18024 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6470 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-98453 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85745 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105083 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-14666 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-14681 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-14666 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-14681 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74604 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-81005 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93117 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98411 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98412 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98445 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98456 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98504 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98506 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98533 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98544 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98588 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98593 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98748 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-25260 | NONE0 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106566 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-14673 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16241 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6469 | NONE0 | libpq-dev 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-14673 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-16241 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6469 | NONE0 | libpq5 17.10-0+deb13u1 fixed in 17.11-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-3374 | NONE0 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-1152 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-107929 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-18924 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80255 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-87862 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87863 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87864 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87865 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87866 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92387 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92389 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92391 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-107929 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-18924 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80255 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-87862 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87863 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87864 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87865 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87866 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92387 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92389 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92391 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-107929 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-18924 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80255 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-87862 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87863 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87864 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87865 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-87866 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92387 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92389 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-92391 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-1152 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109260 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109261 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109263 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109264 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109268 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109271 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61860 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61868 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61871 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-35189 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35191 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | libssl-dev 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-35189 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35191 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41637 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42955 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44687 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46582 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50046 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50243 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54478 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56444 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-77860 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35189 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35191 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-105081 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2-dev 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-94266 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-94266 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-94266 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-66861 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.1-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.1-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3949 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.1-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109267 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109270 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109273 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109277 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56375 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61859 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66011 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93586 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93587 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89162 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89162 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89162 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89162 | NONE0 | libpcre2-dev 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89162 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86141 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86141 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98450 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98451 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98458 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98502 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98509 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98513 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98514 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98528 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98531 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98579 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3479 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-55708 | NONE0 | libunbound8 1.22.0-2+deb13u3 fixed in 1.26.1-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-11731 | NONE0 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11731 | NONE0 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109278 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-61862 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61864 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61865 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61867 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61869 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97618 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18503 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18503 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18503 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18503 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61081 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61081 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61081 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61081 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109258 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109272 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-109274 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109279 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109280 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-109282 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61872 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86424 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98433 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98468 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98527 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98448 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98516 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98535 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98553 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98473 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98505 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98519 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98529 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98594 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45382 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45383 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49295 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49337 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49346 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54240 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54241 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-88373 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.15-1+b3 fixed in 1.0.15-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-A338F9 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | — | Not Applicable |
| TEMP-0000000-FE6BBE | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | — | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88648 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88648 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88648 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-67693 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88647 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-88648 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-62289 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-62292 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-84384 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84446 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84447 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84448 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-84444 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| TEMP-0000000-0F03E5 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-153207 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-18A2CE | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-1B5D39 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-21F713 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-301DE5 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-415AE1 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-4EF776 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-5124DE | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-57F868 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-6C5194 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-78AC20 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-809756 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-8A4B18 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-9253BB | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-956D99 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-BBE297 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-D1A721 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-D2EEB5 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-DB3DE2 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-F2B97A | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-FDE8B2 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-1148137-089975 | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-1148137-126A7B | NONE0 | libheif-plugin-dav1d 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-62289 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-62292 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-84384 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84446 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84447 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84448 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-84444 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| TEMP-0000000-0F03E5 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-153207 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-18A2CE | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-1B5D39 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-21F713 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-301DE5 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-415AE1 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-4EF776 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-5124DE | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-57F868 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-6C5194 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-78AC20 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-809756 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-8A4B18 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-9253BB | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-956D99 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-BBE297 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-D1A721 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-D2EEB5 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-DB3DE2 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-F2B97A | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-FDE8B2 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-1148137-089975 | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-1148137-126A7B | NONE0 | libheif-plugin-libde265 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-62289 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-62292 | NONE0 | libheif1 1.19.8-1 fixed in 1.19.8-1+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-84384 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84446 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84447 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-84448 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-84444 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| TEMP-0000000-0F03E5 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-153207 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-18A2CE | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-1B5D39 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-21F713 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-301DE5 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-415AE1 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-4EF776 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-5124DE | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-57F868 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-6C5194 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-78AC20 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-809756 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-8A4B18 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-9253BB | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-956D99 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-BBE297 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-D1A721 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-0000000-D2EEB5 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-DB3DE2 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-F2B97A | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-0000000-FDE8B2 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| TEMP-1148137-089975 | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| TEMP-1148137-126A7B | NONE0 | libheif1 1.19.8-1 fixed in 1.23.4-1~deb13u1 | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2+deb13u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.16-2+deb13u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| DSA-6549-1 | NONE0 | liblzma-dev 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | liblzma-dev 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| DSA-6549-1 | NONE0 | liblzma5 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | liblzma5 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 fixed in 8:7.1.1.43+dfsg1-1+deb13u12 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106570 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106571 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106572 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106573 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106574 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-106575 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106576 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106578 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-106579 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-106580 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-107208 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107209 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107210 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-109266 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u11 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-85746 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-85746 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-85746 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-2 2.1.28+dfsg1-9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-107161 | NONE0 | libsasl2-modules-db 2.1.28+dfsg1-9 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff-dev 4.7.0-3+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiffxx6 4.7.0-3+deb13u3 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | — | Not Applicable |
| CVE-2026-90037 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68199 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80728 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80891 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89803 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89922 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89943 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89980 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90003 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90048 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90057 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90169 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90375 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90380 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90392 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90398 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92507 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92509 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92510 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92511 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92512 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93148 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93210 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93792 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98084 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64568 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64584 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68120 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68179 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68185 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68192 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68221 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68225 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68302 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68327 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68340 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68359 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68361 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74545 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74691 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80555 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80730 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80731 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80732 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80733 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80736 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80739 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80742 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80743 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80744 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80749 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80752 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80754 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80756 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80757 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80759 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80762 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80763 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80770 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80772 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80774 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80779 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80791 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80815 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80825 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80835 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80838 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80839 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80845 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80860 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80862 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80888 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80889 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80890 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80892 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80893 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80894 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80901 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80904 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80906 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80907 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80908 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80909 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80910 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80911 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80912 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80913 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.105-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80914 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80915 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80916 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80917 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80918 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80922 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80923 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80925 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80926 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-81007 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89562 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89776 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89780 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89781 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89782 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89784 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89785 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89787 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89789 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89792 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89793 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89794 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89796 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89798 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89800 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89801 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89802 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89806 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89807 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89812 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89817 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89818 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89819 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89821 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89823 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89825 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89826 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89827 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89830 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89839 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89842 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89843 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89844 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89845 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89847 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89849 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89850 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89851 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89852 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89853 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89854 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89855 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89856 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89857 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89858 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89861 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89863 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89864 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89865 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89866 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89868 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89871 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89874 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89876 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89878 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89879 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89880 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89883 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89884 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89885 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89887 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89888 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89890 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89891 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89892 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89893 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89895 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89897 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89898 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89901 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89902 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89903 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89904 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89908 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89926 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89927 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89931 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89933 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89934 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89935 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89936 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89937 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89939 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89940 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89941 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89942 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89945 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89946 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89947 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89948 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89949 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89950 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89951 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89952 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89954 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89955 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89957 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89958 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89959 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89961 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89963 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89964 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89968 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-89969 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89971 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89973 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89974 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89979 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89983 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89984 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89986 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89989 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89990 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89992 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89993 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89994 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89995 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89997 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89999 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90000 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90001 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90012 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90017 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90018 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90019 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90020 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90024 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90025 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90026 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90030 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90031 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90032 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90033 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90034 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90035 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90039 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90040 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90041 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90042 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90153 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90329 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90353 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90357 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90358 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90360 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90366 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90368 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90370 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90372 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90373 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90374 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90382 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90386 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90387 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90388 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90391 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90393 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90394 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90395 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90397 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90399 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90400 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90403 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90409 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90413 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-90416 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90419 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90420 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90426 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90428 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90430 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90431 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90435 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92476 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92477 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92484 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92489 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-92490 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92491 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92495 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92496 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92497 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92498 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92501 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92502 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92506 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92508 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92514 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92515 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92518 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92521 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92522 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-92523 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92525 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93037 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93039 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93040 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93041 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93044 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93045 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93046 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93048 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93049 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93051 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93052 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93053 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93054 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93055 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93061 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93063 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93064 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93065 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93067 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93070 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93073 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93084 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93085 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93086 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93092 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93095 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93097 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93098 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93103 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93107 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93108 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93109 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93110 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93113 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93114 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93115 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93118 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93119 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93120 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93121 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93131 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93132 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93133 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93134 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93135 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93137 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93138 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93140 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93141 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93149 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93152 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93156 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93158 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93160 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93162 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93165 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93167 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93170 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93173 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93174 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93177 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93178 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93182 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93183 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93184 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93206 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93208 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93209 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93211 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93212 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93213 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93214 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93215 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93219 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93222 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93223 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93224 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-93226 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93229 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93234 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93236 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93238 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93242 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93245 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93247 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93250 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93252 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93256 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93259 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93781 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93783 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93784 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93797 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97445 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97449 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97450 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97452 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97453 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97454 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97520 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97568 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97605 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98076 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98077 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98081 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98083 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98086 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98088 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98089 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98090 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98091 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98094 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98095 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98096 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98097 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98098 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98232 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98316 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64583 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68124 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-68151 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68213 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68220 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68223 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68314 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68370 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.101-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89799 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89822 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89834 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89835 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89848 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89860 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89870 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89899 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89929 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89938 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89960 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89962 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89988 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89998 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90022 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90027 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90044 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90045 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90351 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90363 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90367 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90383 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90385 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90389 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90408 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90410 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90418 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90433 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92481 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93042 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93050 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93062 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93091 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93093 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93123 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93128 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93142 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93150 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93155 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93163 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93172 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93181 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93205 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93230 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93235 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93239 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93240 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93810 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98102 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.111-1 | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98479 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98481 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98482 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98483 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98484 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98485 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98486 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98487 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98488 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98489 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98490 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98491 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98493 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98494 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98495 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98498 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98499 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98601 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98602 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98605 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98606 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98607 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98608 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98609 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98610 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98611 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98612 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98613 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98614 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98615 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98616 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98618 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98620 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98621 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98622 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98623 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98624 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98625 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98626 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98629 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98631 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98632 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98634 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98636 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98640 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98641 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98642 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98643 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98644 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98646 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98647 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98655 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98656 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98657 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98658 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98660 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98661 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98663 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98664 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98665 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98666 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98668 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98669 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98670 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98671 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98672 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98673 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98674 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98677 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98679 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98680 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98681 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98686 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98687 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98694 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98695 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98696 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98697 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98698 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98699 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98700 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98701 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98703 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98704 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98705 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98706 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98707 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98708 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98709 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98710 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98713 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98716 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98717 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98720 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98721 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98722 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98725 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98726 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98727 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98728 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98730 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98731 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98732 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98733 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98734 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98735 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98736 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98737 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98738 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98739 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98741 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98742 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98743 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98744 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98745 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98746 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98747 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98750 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98751 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98752 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98753 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98754 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98755 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98756 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98757 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98758 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98760 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98761 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98762 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98763 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98764 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98765 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98766 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98767 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98769 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98770 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98771 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98772 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98773 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98775 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98777 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98778 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98779 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98780 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98781 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98782 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98783 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98784 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98785 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98790 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98791 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98792 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98793 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98794 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98796 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98797 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98798 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98805 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98807 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98808 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98809 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98811 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98812 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98813 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98819 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98822 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98823 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98825 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98827 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98828 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98830 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98831 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98833 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98835 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98836 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98837 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98838 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98840 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98841 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98843 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98844 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98845 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98846 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98847 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98848 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98849 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98850 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98851 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98852 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| CVE-2026-98854 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98855 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98856 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98857 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98858 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98859 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98860 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98862 | NONE0 | linux-libc-dev 6.12.100-1 fixed in 6.12.113-1 | — | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.12.100-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-85746 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-92262 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| TEMP-1142904-117334 | NONE0 | unzip 6.0-29 fixed in 6.0-29+deb13u1 | — | Not Applicable |
| TEMP-1142905-081994 | NONE0 | unzip 6.0-29 fixed in 6.0-29+deb13u1 | — | Not Applicable |
| DSA-6440-1 | NONE0 | unzip 6.0-29 fixed in 6.0-29+deb13u1 | — | Not Applicable |
| TEMP-1142906-2C6C79 | NONE0 | unzip 6.0-29 fixed in 6.0-29+deb13u1 | — | Not Applicable |
| DSA-6549-1 | NONE0 | xz-utils 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | xz-utils 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.