This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve unauthorized remote code execution during repository cloning via CVE-2026-42284, potentially compromising the entire container. Several other high-severity vulnerabilities, such as CVE-2026-8376, also contribute to a large attack surface with 119 exposed flaws rated 7.0 or higher. While this is an official Docker image, the sheer volume and critical nature of these vulnerabilities make it fundamentally unsafe for production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-8376 | CRITICAL9.8 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-7210 | CRITICAL9.8 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-42284 | CRITICAL9.8 | python3-git 3.1.44-1 No fix yet | — | Directly ExposedContext importance: HIGH |
| CVE-2009-3546 | CRITICAL9.3 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2009-3546 | CRITICAL9.3 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2009-3546 | CRITICAL9.3 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42216 | CRITICAL9.1 | libopenexr-3-1-30 3.1.13-2 No fix yet | — | Directly Exposed |
| CVE-2026-42216 | CRITICAL9.1 | libopenexr-dev 3.1.13-2 No fix yet | — | Directly Exposed |
| CVE-2026-42496 | CRITICAL9.1 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-32740 | HIGH8.8 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32740 | HIGH8.8 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32740 | HIGH8.8 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-41142 | HIGH8.8 | libopenexr-3-1-30 3.1.13-2 No fix yet | — | Directly Exposed |
| CVE-2026-41142 | HIGH8.8 | libopenexr-dev 3.1.13-2 No fix yet | — | Directly Exposed |
| CVE-2019-1010022 | HIGH8.33 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | HIGH8.33 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | HIGH8.33 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | HIGH8.33 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-20884 | HIGH8.33 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24450 | HIGH8.33 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24660 | HIGH8.33 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | HIGH8.1 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-41071 | HIGH8.1 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-41071 | HIGH8.1 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2023-34152 | HIGH8 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH8 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | HIGH7.84 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2007-3996 | HIGH7.82 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 15.1% High Exploitation Risk | Directly Exposed |
| CVE-2007-3996 | HIGH7.82 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 15.1% High Exploitation Risk | Directly Exposed |
| CVE-2007-3996 | HIGH7.82 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 15.1% High Exploitation Risk | Directly Exposed |
| CVE-2026-48962 | HIGH7.8 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.12.88-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46243 | HIGH7.8 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-2 | — | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46274 | HIGH7.8 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-7598 | HIGH7.73 | libssh2-1-dev 1.11.1-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | HIGH7.73 | libssh2-1t64 1.11.1-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | krb5-multidev 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5773 | HIGH7.5 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6276 | HIGH7.5 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-5773 | HIGH7.5 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6276 | HIGH7.5 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-5773 | HIGH7.5 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6276 | HIGH7.5 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-45186 | HIGH7.5 | libexpat1 2.7.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-45186 | HIGH7.5 | libexpat1-dev 2.7.1-2 No fix yet | — | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssrpc4t64 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5clnt-mit12 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5srv-mit12 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkdb5-10t64 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-dev 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-dev 2.6.10+dfsg-1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-dev 2.6.10+dfsg-1 No fix yet | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 6.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42497 | HIGH7.5 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-9538 | HIGH7.5 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40622 | HIGH7.5 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-41292 | HIGH7.5 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-42944 | HIGH7.5 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-42959 | HIGH7.5 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-9580 | HIGH7.48 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9581 | HIGH7.48 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-16376 | HIGH7.48 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2016-9580 | HIGH7.48 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9581 | HIGH7.48 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-16376 | HIGH7.48 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | HIGH7.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-32741 | HIGH7.1 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32882 | HIGH7.1 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32741 | HIGH7.1 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32882 | HIGH7.1 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32741 | HIGH7.1 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32882 | HIGH7.1 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-43414 | HIGH7.1 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46209 | HIGH7.1 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2008-4609 | HIGH7.1 | linux-libc-dev 6.12.88-1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43198 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43494 | HIGH7 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-2 | — | Directly Exposed |
| CVE-2026-43503 | HIGH7 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-45932 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46054 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46117 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46181 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46227 | HIGH7 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-43303 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45840 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45934 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46017 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46032 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46158 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46160 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46170 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46242 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46275 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2025-71313 | HIGH7 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libdw1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libdw1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12495 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12495 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19449 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19814 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31688 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19378 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25265 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | MEDIUM6.5 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6429 | MEDIUM6.5 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-5545 | MEDIUM6.5 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6429 | MEDIUM6.5 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-5545 | MEDIUM6.5 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6429 | MEDIUM6.5 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-32738 | MEDIUM6.5 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32739 | MEDIUM6.5 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32814 | MEDIUM6.5 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32738 | MEDIUM6.5 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32739 | MEDIUM6.5 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32814 | MEDIUM6.5 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32738 | MEDIUM6.5 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32739 | MEDIUM6.5 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2026-32814 | MEDIUM6.5 | libheif1 1.19.8-1 No fix yet | — | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33164 | MEDIUM6.38 | libde265-0 1.0.15-1+b3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdw1t64 0.192-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.192-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.11.0-7 fixed in 1.11.0-7+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | MEDIUM6.38 | libgcrypt20 1.11.0-7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-36325 | MEDIUM6.38 | libjansson4 2.14-2+b3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-dev 3.1.13-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-9113 | MEDIUM6.38 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9114 | MEDIUM6.38 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-9113 | MEDIUM6.38 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9114 | MEDIUM6.38 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-20889 | MEDIUM6.38 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-21413 | MEDIUM6.38 | libraw23t64 0.21.4-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19070 | MEDIUM6.38 | linux-libc-dev 6.12.88-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-0400 | MEDIUM6.38 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-34152 | MEDIUM6.11 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2023-34152 | MEDIUM6.11 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2023-34152 | MEDIUM6.11 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 75.0% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2026-43197 | MEDIUM6.1 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif-plugin-dav1d 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif-plugin-libde265 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif1 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42960 | MEDIUM6 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.9 | libexpat1 2.7.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.9 | libexpat1-dev 2.7.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-44608 | MEDIUM5.9 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.88-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42217 | MEDIUM5.88 | libopenexr-3-1-30 3.1.13-2 No fix yet | — | Directly Exposed |
| CVE-2026-42217 | MEDIUM5.88 | libopenexr-dev 3.1.13-2 No fix yet | — | Directly Exposed |
| CVE-2026-33278 | MEDIUM5.88 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-8376 | MEDIUM5.88 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | MEDIUM5.88 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | MEDIUM5.88 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-7210 | MEDIUM5.88 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-7210 | MEDIUM5.88 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-1965 | MEDIUM5.78 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM5.78 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM5.78 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-dev 2.6.10+dfsg-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15778 | MEDIUM5.77 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 64.3% Actively Exploited | Post-Exploit |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM5.52 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM5.52 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM5.52 | libcairo2 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM5.52 | libcairo2-dev 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | MEDIUM5.52 | libjbig-dev 2.1-6.1+b2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | MEDIUM5.52 | libjbig0 2.1-6.1+b2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2017-11754 | MEDIUM5.52 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11755 | MEDIUM5.52 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-15607 | MEDIUM5.52 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2016-9115 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9116 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2016-9117 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-6988 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2016-9115 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9116 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2016-9117 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-6988 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-dev 0.44.0-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-10126 | MEDIUM5.52 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1210 | MEDIUM5.52 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-10126 | MEDIUM5.52 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1210 | MEDIUM5.52 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-10126 | MEDIUM5.52 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-1210 | MEDIUM5.52 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2026-42050 | MEDIUM5.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Directly Exposed |
| CVE-2025-71285 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2025-71289 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2025-71302 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43127 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43172 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43191 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43204 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43213 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43216 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43219 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43234 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43272 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43294 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43298 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43299 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43301 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43308 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43309 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43310 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43311 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43325 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43326 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43331 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43337 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43344 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43346 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43352 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43353 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43355 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43416 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43443 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43463 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43464 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-43465 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45836 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-45838 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45841 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45842 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45843 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45844 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45845 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45846 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45944 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46066 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46093 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46111 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46130 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46137 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46159 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46191 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46207 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46214 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46234 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46252 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46312 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2025-71315 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45897 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45901 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45961 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-45963 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46014 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46059 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46071 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46092 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46153 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46201 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46203 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46216 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46235 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-46256 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46279 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46302 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | — | Directly Exposed |
| CVE-2026-46313 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Directly Exposed |
| CVE-2026-42496 | MEDIUM5.46 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3805 | MEDIUM5.35 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3805 | MEDIUM5.35 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3805 | MEDIUM5.35 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-6110 | MEDIUM5.3 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 57.6% Actively Exploited | Post-Exploit |
| CVE-2026-4873 | MEDIUM5.3 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6253 | MEDIUM5.3 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-7168 | MEDIUM5.3 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-4873 | MEDIUM5.3 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6253 | MEDIUM5.3 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-7168 | MEDIUM5.3 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-4873 | MEDIUM5.3 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-6253 | MEDIUM5.3 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-7168 | MEDIUM5.3 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-3276 | MEDIUM5.3 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-32792 | MEDIUM5.3 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-42534 | MEDIUM5.3 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-42923 | MEDIUM5.3 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-44390 | MEDIUM5.3 | libunbound8 1.22.0-2+deb13u2 fixed in 1.22.0-2+deb13u3 | — | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-6951 | MEDIUM5.17 | patch 2.8-2 No fix yet | 15.3% High Exploitation Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM5.17 | patch 2.8-2 No fix yet | 11.8% High Exploitation Risk | Post-Exploit |
| CVE-2026-40355 | MEDIUM5.02 | krb5-multidev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | krb5-multidev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-multidev 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | krb5-multidev 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.02 | libgcrypt20 1.11.0-7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5-3 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-dev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-dev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-dev 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5-dev 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.02 | libtasn1-6 4.20.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.02 | libtasn1-6-dev 4.20.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.02 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | — | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-dev 1.0.8-6 No fix yet | — | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM5 | linux-libc-dev 6.12.88-1 No fix yet | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3783 | MEDIUM4.84 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | MEDIUM4.84 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | MEDIUM4.84 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | MEDIUM4.8 | tar 1.35+dfsg-3.1 No fix yet | 3.8% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-60753 | MEDIUM4.67 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM4.67 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM4.67 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM4.67 | libcairo2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM4.67 | libcairo2-dev 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libdw1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libdw1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-7275 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14988 | MEDIUM4.67 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14988 | MEDIUM4.67 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-24890 | MEDIUM4.67 | libraw23t64 0.21.4-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2193 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31435 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31562 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31732 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.5 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-6276 | MEDIUM4.5 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2023-30571 | MEDIUM4.5 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM4.5 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM4.5 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma-dev 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng-dev 1.6.48-1+deb13u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5342 | MEDIUM4.5 | libraw23t64 0.21.4-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-9019 | MEDIUM4.5 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2015-9019 | MEDIUM4.5 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44243 | MEDIUM4.26 | python3-git 3.1.44-1 No fix yet | — | Post-Exploit |
| CVE-2012-0039 | MEDIUM4.25 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33165 | MEDIUM4.25 | libde265-0 1.0.15-1+b3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-3-1-30 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-dev 3.1.13-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM4.25 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | MEDIUM4.08 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | MEDIUM4.08 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | MEDIUM4.08 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdw1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23469 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31456 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | uuid-dev 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | dirmngr 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gnupg 2.4.7-21+deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgsm 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-6429 | LOW3.9 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 4.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-24975 | LOW3.82 | git 1:2.47.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW3.82 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2016-20012 | LOW3.66 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 14.6% High Exploitation Risk | Post-Exploit |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.65 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.65 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | LOW3.57 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | LOW3.57 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libdw1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.31 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-11754 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2017-11755 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-15607 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2017-11754 | LOW3.31 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2017-11755 | LOW3.31 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-15607 | LOW3.31 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2017-11754 | LOW3.31 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2017-11755 | LOW3.31 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-15607 | LOW3.31 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-42050 | LOW3.3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Post-Exploit |
| CVE-2026-42050 | LOW3.3 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Post-Exploit |
| CVE-2026-42050 | LOW3.3 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW3.18 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-6253 | LOW3.18 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2026-7168 | LOW3.18 | curl 8.14.1-2+deb13u3 No fix yet | — | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-3276 | LOW3.18 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.11 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW3 | bzip2 1.0.8-6 No fix yet | — | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-8678 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-7275 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-8678 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-7275 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-8678 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-7275 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.18.4-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.18.4-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2-dev 1.18.4-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif-plugin-dav1d 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif-plugin-libde265 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif1 1.19.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW2.55 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW2.55 | git 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW2.55 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW2.55 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW2.55 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2007-2243 | LOW2.55 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login.defs 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.4.7-21+deb13u1+b3 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+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW2.29 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2768 | LOW2.19 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | login.defs 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24515 | LOW2.12 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.4.7-21+deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.4.7-21+deb13u1+b3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-29 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24882 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.4% 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-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-42326 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-2+b1 No fix yet | — | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-dev 1.3.14-2+b1 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2+deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.16-2+deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u8 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | — | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44170 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44170 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44170 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl-dev 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | 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-31536 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-44168 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44170 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44171 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44172 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-44173 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48163 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-48165 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-49261 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-42215 | NONE0 | python3-git 3.1.44-1 No fix yet | — | Not Applicable |
| CVE-2026-44244 | NONE0 | python3-git 3.1.44-1 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-7774 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-9669 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |