Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. An attacker could exploit ImageMagick heap overflow (CVE-2026-56372) to leak sensitive data or cause denial of service, and the glibc issue (CVE-2019-1010023) may enable code execution if ldd is run on a malicious ELF. Disabling ImageMagick or restricting its use would fully mitigate the highest-severity findings. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-56372 | CRITICAL9.1 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.41-12+deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.41-12+deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2005 | HIGH8.8 | libpq5 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2006 | HIGH8.8 | libpq5 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42960 | HIGH8.5 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32710 | HIGH8.42 | libmariadb3 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | perl-base 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | perl-modules-5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-22770 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23876 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25897 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25971 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25983 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25986 | HIGH8.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22770 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23876 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25897 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25971 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25983 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25986 | HIGH8.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22770 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23876 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25897 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25971 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25983 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25986 | HIGH8.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22770 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23876 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25897 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25971 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25983 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25986 | HIGH8.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22770 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23876 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25897 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25971 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25983 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25986 | HIGH8.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22770 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23876 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-25897 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25971 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25983 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25986 | HIGH8.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49261 | HIGH8.33 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42217 | HIGH8.33 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-20884 | HIGH8.33 | libraw23t64 0.21.4-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-24450 | HIGH8.33 | libraw23t64 0.21.4-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-24660 | HIGH8.33 | libraw23t64 0.21.4-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42257 | HIGH8.33 | net-imap 0.3.9 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27820 | HIGH8.33 | zlib 3.0.0 fixed in ~> 3.0.1, ~> 3.1.2, >= 3.2.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | HIGH7.73 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25987 | HIGH7.73 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26284 | HIGH7.73 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | HIGH7.73 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25987 | HIGH7.73 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26284 | HIGH7.73 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | HIGH7.73 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25987 | HIGH7.73 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26284 | HIGH7.73 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | HIGH7.73 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25987 | HIGH7.73 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26284 | HIGH7.73 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | HIGH7.73 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25987 | HIGH7.73 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26284 | HIGH7.73 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | HIGH7.73 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25987 | HIGH7.73 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26284 | HIGH7.73 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH7.73 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42216 | HIGH7.73 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | gir1.2-gdkpixbuf-2.0 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46522 | HIGH7.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-46522 | HIGH7.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.11.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf2.0-bin 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssrpc4t64 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5clnt-mit12 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5srv-mit12 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkdb5-10t64 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46522 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-46522 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-46522 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-46522 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33416 | HIGH7.5 | libpng16-16t64 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3+deb13u1 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif1 1.19.8-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41142 | HIGH7.48 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2004 | HIGH7.48 | libpq5 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6473 | HIGH7.48 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6637 | HIGH7.48 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6638 | HIGH7.48 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6477 | HIGH7.14 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25794 | MEDIUM6.97 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25794 | MEDIUM6.97 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25794 | MEDIUM6.97 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25794 | MEDIUM6.97 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25794 | MEDIUM6.97 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25794 | MEDIUM6.97 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6478 | MEDIUM6.97 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28693 | MEDIUM6.88 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28693 | MEDIUM6.88 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28693 | MEDIUM6.88 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28693 | MEDIUM6.88 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28693 | MEDIUM6.88 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28693 | MEDIUM6.88 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng16-16t64 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u3 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM6.8 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25966 | MEDIUM6.63 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30883 | MEDIUM6.63 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30929 | MEDIUM6.63 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30931 | MEDIUM6.63 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25966 | MEDIUM6.63 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30883 | MEDIUM6.63 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30929 | MEDIUM6.63 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30931 | MEDIUM6.63 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32775 | MEDIUM6.63 | libexif12 0.6.25-1 fixed in 0.6.25-1+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25966 | MEDIUM6.63 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30883 | MEDIUM6.63 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30929 | MEDIUM6.63 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30931 | MEDIUM6.63 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25966 | MEDIUM6.63 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30883 | MEDIUM6.63 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30929 | MEDIUM6.63 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30931 | MEDIUM6.63 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25966 | MEDIUM6.63 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30883 | MEDIUM6.63 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30929 | MEDIUM6.63 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30931 | MEDIUM6.63 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25966 | MEDIUM6.63 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30883 | MEDIUM6.63 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30929 | MEDIUM6.63 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30931 | MEDIUM6.63 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb3 1:11.8.3-0+deb13u1 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng16-16t64 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u1 fixed in 4.7.0-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u1 fixed in 4.7.0-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1+b2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng16-16t64 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23952 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25795 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25796 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25798 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25799 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25965 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25967 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25969 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25970 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25985 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25988 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26066 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26283 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28691 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32636 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33900 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33901 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33908 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45031 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45664 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46520 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46523 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24485 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25989 | MEDIUM6.38 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23952 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25795 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25796 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25798 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25799 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25965 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25967 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25969 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25970 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25985 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25988 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26066 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26283 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28691 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32636 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33900 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33901 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33908 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45031 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45664 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46520 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46523 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24485 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25989 | MEDIUM6.38 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33164 | MEDIUM6.38 | libde265-0 1.0.15-1+b3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.192-4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.11.0-7 fixed in 1.11.0-7+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssrpc4t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssrpc4t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkadm5clnt-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkadm5clnt-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkadm5srv-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkadm5srv-mit12 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkdb5-10t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkdb5-10t64 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | liblcms2-2 2.16-2 fixed in 2.16-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23952 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25795 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25796 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25798 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25799 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25965 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25967 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25969 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25970 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25985 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25988 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26066 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26283 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28691 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32636 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33900 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33901 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33908 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45031 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45664 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46520 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46523 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24485 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25989 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23952 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25795 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25796 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25798 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25799 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25965 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25967 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25969 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25970 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25985 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25988 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26066 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26283 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28691 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32636 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33900 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33901 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33908 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45031 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45664 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46520 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46523 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24485 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25989 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23952 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25795 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25796 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25798 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25799 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25965 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25967 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25969 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25970 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25985 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25988 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26066 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26283 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28691 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32636 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33900 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33901 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33908 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45031 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45664 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46520 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46523 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24485 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25989 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23952 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25795 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25796 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25798 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25799 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25965 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25967 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25969 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25970 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25985 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25988 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-26066 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26283 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28691 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32636 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33900 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33901 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33908 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45031 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45664 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46520 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46523 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24485 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25989 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.64.0-1.1 fixed in 1.64.0-1.1+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libngtcp2-16 1.11.0-1 fixed in 1.11.0-1+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libngtcp2-crypto-gnutls8 1.11.0-1 fixed in 1.11.0-1+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6479 | MEDIUM6.38 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-20889 | MEDIUM6.38 | libraw23t64 0.21.4-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-21413 | MEDIUM6.38 | libraw23t64 0.21.4-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40622 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41292 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42944 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42959 | MEDIUM6.38 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42245 | MEDIUM6.38 | net-imap 0.3.9 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61594 | MEDIUM6.38 | uri 0.12.4 fixed in ~> 0.12.5, ~> 0.13.3, >= 1.0.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42246 | MEDIUM6.29 | net-imap 0.3.9 fixed in ~> 0.3.10, ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-6476 | MEDIUM6.12 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27798 | MEDIUM6.03 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33905 | MEDIUM6.03 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45359 | MEDIUM6.03 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28494 | MEDIUM6.03 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27798 | MEDIUM6.03 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33905 | MEDIUM6.03 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45359 | MEDIUM6.03 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28494 | MEDIUM6.03 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40385 | MEDIUM6.03 | libexif12 0.6.25-1 fixed in 0.6.25-1+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40386 | MEDIUM6.03 | libexif12 0.6.25-1 fixed in 0.6.25-1+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27798 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33905 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45359 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28494 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27798 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33905 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45359 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28494 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27798 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33905 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45359 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28494 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27798 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33905 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45359 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28494 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng16-16t64 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.75-10+b3 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.11.0-7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssrpc4t64 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5clnt-mit12 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5srv-mit12 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkdb5-10t64 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28686 | MEDIUM5.78 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28686 | MEDIUM5.78 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 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-2026-28686 | MEDIUM5.78 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28686 | MEDIUM5.78 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28686 | MEDIUM5.78 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28686 | MEDIUM5.78 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6475 | MEDIUM5.7 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-dane0t64 3.8.9-3+deb13u1 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-openssl27t64 3.8.9-3+deb13u1 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u1 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-25982 | MEDIUM5.52 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28493 | MEDIUM5.52 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28690 | MEDIUM5.52 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56366 | MEDIUM5.52 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25982 | MEDIUM5.52 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28493 | MEDIUM5.52 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28690 | MEDIUM5.52 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56366 | MEDIUM5.52 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 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.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49271 | MEDIUM5.52 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49271 | MEDIUM5.52 | libheif-plugin-libde265 1.19.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif1 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49271 | MEDIUM5.52 | libheif1 1.19.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25982 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28493 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28690 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56366 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25982 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28493 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28690 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56366 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25982 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28493 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28690 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56366 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25982 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28493 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28690 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56366 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34303 | MEDIUM5.52 | libmariadb3 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35549 | MEDIUM5.52 | libmariadb3 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-24890 | MEDIUM5.5 | libraw23t64 0.21.4-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28689 | MEDIUM5.35 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28689 | MEDIUM5.35 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28689 | MEDIUM5.35 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28689 | MEDIUM5.35 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28689 | MEDIUM5.35 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28689 | MEDIUM5.35 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.7.1-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.35-1.2+deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46559 | MEDIUM5.27 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46559 | MEDIUM5.27 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46559 | MEDIUM5.27 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46559 | MEDIUM5.27 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46559 | MEDIUM5.27 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46559 | MEDIUM5.27 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30937 | MEDIUM5.18 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30937 | MEDIUM5.18 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30937 | MEDIUM5.18 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30937 | MEDIUM5.18 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30937 | MEDIUM5.18 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30937 | MEDIUM5.18 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | MEDIUM5.18 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | MEDIUM5.18 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47240 | MEDIUM5.18 | net-imap 0.3.9 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47166 | MEDIUM5.1 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47166 | MEDIUM5.1 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47166 | MEDIUM5.1 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47166 | MEDIUM5.1 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47166 | MEDIUM5.1 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47166 | MEDIUM5.1 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46692 | MEDIUM5.02 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46692 | MEDIUM5.02 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46692 | MEDIUM5.02 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46692 | MEDIUM5.02 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46692 | MEDIUM5.02 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46692 | MEDIUM5.02 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44608 | MEDIUM5.02 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47241 | MEDIUM5.02 | net-imap 0.3.9 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25968 | MEDIUM5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-25971 | MEDIUM5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-25983 | MEDIUM5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25986 | MEDIUM5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | MEDIUM5 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | MEDIUM5 | gir1.2-glib-2.0 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libgirepository-2.0-0 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-bin 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-data 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41316 | MEDIUM4.86 | erb 4.0.2 fixed in ~> 4.0.3.1, ~> 4.0.4.1, ~> 6.0.1.1, >= 6.0.4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-60002 | MEDIUM4.79 | openssh-client 1:10.0p1-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-6110 | MEDIUM4.69 | openssh-client 1:10.0p1-7 No fix yet | 20.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-23874 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25576 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30935 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30936 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31853 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33535 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33902 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34238 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40169 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40183 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40310 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40311 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40312 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46521 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56379 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46557 | MEDIUM4.67 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23874 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25576 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30935 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30936 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31853 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33535 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33902 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34238 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40169 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40183 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40310 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40311 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40312 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46521 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56379 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46557 | MEDIUM4.67 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% 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 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% 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 | libelf1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% 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.2% 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-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23874 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25576 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30935 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30936 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31853 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33535 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33902 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34238 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40169 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40183 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40310 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40311 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40312 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46521 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56379 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46557 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23874 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25576 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30935 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30936 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31853 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33535 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33902 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34238 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40169 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40183 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40310 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40311 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40312 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46521 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56379 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46557 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23874 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25576 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30935 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30936 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31853 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33535 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33902 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34238 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40169 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40183 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40310 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40311 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40312 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46521 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56379 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46557 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23874 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25576 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-30935 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30936 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31853 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33535 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33902 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34238 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40169 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40183 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40310 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40311 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40312 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42050 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46521 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56379 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46557 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14988 | MEDIUM4.67 | libopenexr-3-1-30 3.1.13-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1.2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15469 | MEDIUM4.67 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25898 | MEDIUM4.64 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-25987 | MEDIUM4.64 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-26284 | MEDIUM4.64 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56367 | MEDIUM4.64 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-1489 | MEDIUM4.59 | gir1.2-glib-2.0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libgirepository-2.0-0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-data 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6472 | MEDIUM4.59 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46522 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-61857 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-61861 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-61870 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3497 | MEDIUM4.5 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22693 | MEDIUM4.5 | gir1.2-harfbuzz-0.0 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24484 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25637 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25638 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25797 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26983 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28687 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28688 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32259 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33899 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45358 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56373 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24484 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25637 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25638 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25797 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26983 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28687 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28688 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32259 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33899 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45358 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56373 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 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.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-23865 | MEDIUM4.5 | libfreetype6 2.13.3+dfsg-1 fixed in 2.13.3+dfsg-1+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz-cairo0 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz-gobject0 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz-icu0 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz-subset0 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24484 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25637 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25638 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25797 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26983 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28687 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28688 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32259 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33899 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45358 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56373 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24484 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25637 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25638 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25797 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26983 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28687 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28688 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32259 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33899 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45358 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56373 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24484 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25637 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25638 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25797 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26983 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28687 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28688 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32259 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33899 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45358 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56373 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24484 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25637 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25638 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25797 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26983 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28687 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28688 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32259 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33899 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45358 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56373 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 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.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5342 | MEDIUM4.5 | libraw23t64 0.21.4-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32792 | MEDIUM4.5 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42534 | MEDIUM4.5 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42923 | MEDIUM4.5 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44390 | MEDIUM4.5 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42258 | MEDIUM4.5 | net-imap 0.3.9 fixed in ~> 0.4.24, ~> 0.5.14, >= 0.6.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-58767 | MEDIUM4.5 | rexml 3.3.9 fixed in >= 3.4.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42326 | MEDIUM4.33 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42326 | MEDIUM4.33 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42326 | MEDIUM4.33 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42326 | MEDIUM4.33 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42326 | MEDIUM4.33 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42326 | MEDIUM4.33 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.6% 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.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.6% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssrpc4t64 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5clnt-mit12 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5srv-mit12 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkdb5-10t64 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-3-1-30 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25794 | MEDIUM4.18 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56378 | MEDIUM4.18 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28693 | MEDIUM4.13 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-35385 | MEDIUM4.13 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-35386 | MEDIUM4.13 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35414 | MEDIUM4.13 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-28692 | MEDIUM4.08 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28692 | MEDIUM4.08 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28692 | MEDIUM4.08 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28692 | MEDIUM4.08 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28692 | MEDIUM4.08 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28692 | MEDIUM4.08 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2026-33536 | MEDIUM4 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33536 | MEDIUM4 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <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-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33536 | MEDIUM4 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33536 | MEDIUM4 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33536 | MEDIUM4 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33536 | MEDIUM4 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <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-2025-68160 | MEDIUM4 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | dirmngr 2.4.7-21+deb13u1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg 2.4.7-21+deb13u1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg-agent 2.4.7-21+deb13u1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgconf 2.4.7-21+deb13u1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgsm 2.4.7-21+deb13u1+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25966 | LOW3.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-30883 | LOW3.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-30929 | LOW3.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-30931 | LOW3.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56370 | LOW3.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | curl 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-61465 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2017-11754 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11755 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15607 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:10.0p1-7 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmf-0.2-7 0.2.13-1.1+b3 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmflite-0.2-7 0.2.13-1.1+b3 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23952 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25795 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25796 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25798 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25799 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25965 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-25967 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-25969 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25970 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-25985 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-25988 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-26066 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26283 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28691 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32636 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33900 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33901 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33908 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45031 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45664 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46520 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46523 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-49218 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53460 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53461 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56368 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24485 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25989 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59999 | LOW3.82 | openssh-client 1:10.0p1-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:10.0p1-7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW3.82 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.13 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.13-minimal 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27799 | LOW3.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45624 | LOW3.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46693 | LOW3.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27799 | LOW3.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45624 | LOW3.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46693 | LOW3.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27799 | LOW3.74 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45624 | LOW3.74 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46693 | LOW3.74 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27799 | LOW3.74 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45624 | LOW3.74 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46693 | LOW3.74 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27799 | LOW3.74 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45624 | LOW3.74 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46693 | LOW3.74 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27799 | LOW3.74 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45624 | LOW3.74 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46693 | LOW3.74 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16t64 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3494 | LOW3.65 | libmariadb3 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb3 1:11.8.3-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2003 | LOW3.65 | libpq5 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6474 | LOW3.65 | libpq5 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27798 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33905 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45359 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56361 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56374 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28494 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | gir1.2-glib-2.0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | LOW3.57 | libgirepository-2.0-0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | LOW3.57 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | LOW3.57 | libglib2.0-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | LOW3.57 | libglib2.0-data 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:10.0p1-7 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-33278 | LOW3.53 | libunbound8 1.22.0-2+deb13u1 fixed in 1.22.0-2+deb13u3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28686 | LOW3.47 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-47165 | LOW3.4 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47165 | LOW3.4 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47165 | LOW3.4 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47165 | LOW3.4 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47165 | LOW3.4 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47165 | LOW3.4 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | binutils 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.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-25982 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28493 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28690 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53466 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56366 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35387 | LOW3.31 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59998 | LOW3.31 | openssh-client 1:10.0p1-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:10.0p1-7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2673 | LOW3.31 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8678 | LOW3.3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7275 | LOW3.3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56372 | LOW3.28 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28689 | LOW3.21 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-2 fixed in 4.9-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-61858 | LOW3.18 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:10.0p1-7 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:10.0p1-7 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46559 | LOW3.16 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0988 | LOW3.15 | gir1.2-glib-2.0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libgirepository-2.0-0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-data 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls-dane0t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls-openssl27t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30t64 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-30937 | LOW3.11 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55628 | LOW3.11 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11187 | LOW3.11 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:10.0p1-7 No fix yet | 13.0% High Exploitation Risk | Post-Exploit |
| CVE-2026-47166 | LOW3.06 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-46692 | LOW3.01 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48994 | LOW3.01 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55577 | LOW3.01 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15468 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66199 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.25.0-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-22770 | LOW3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-23876 | LOW3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-25897 | LOW3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:10.0p1-7 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% 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.4% Theoretical Threat | Post-Exploit |
| CVE-2026-23874 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-25576 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-30935 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-30936 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31853 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33535 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33902 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34238 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40169 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40183 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40310 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40311 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40312 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42050 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46521 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48724 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48734 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55597 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56379 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-46557 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15469 | LOW2.8 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53464 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-script-interpreter2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.18.4-1+b1 No fix yet | 0.2% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% 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-2026-53464 | LOW2.8 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6192 | LOW2.8 | libopenjp2-7 2.5.3-2.1~deb13u1 fixed in 2.5.3-2.1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | LOW2.75 | openssh-client 1:10.0p1-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:10.0p1-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:10.0p1-7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-24484 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25637 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-25638 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-25797 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-26983 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28687 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28688 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-32259 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33899 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45358 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53467 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55594 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56365 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56371 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56373 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-61984 | LOW2.7 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-61985 | LOW2.7 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13-minimal 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1.2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42326 | LOW2.6 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:10.0p1-7 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.6% 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.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% 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-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28692 | LOW2.45 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.4.7-21+deb13u1+b1 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+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-33536 | LOW2.4 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55595 | LOW2.4 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | gir1.2-glib-2.0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Directly Exposed |
| 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libgirepository-2.0-0 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libglib2.0-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libglib2.0-data 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27799 | LOW2.24 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45624 | LOW2.24 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-46693 | LOW2.24 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56362 | LOW2.14 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-49219 | LOW2.14 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47165 | LOW2.04 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-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.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% 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.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.4.7-21+deb13u1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.4.7-21+deb13u1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.4.7-21+deb13u1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+deb13u1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.4.7-21+deb13u1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53464 | LOW1.68 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56363 | LOW1.68 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56376 | LOW1.68 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56377 | LOW1.68 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-29 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56364 | LOW1.61 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | dirmngr 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-agent 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgconf 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgsm 2.4.7-21+deb13u1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-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.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35388 | LOW1.27 | openssh-client 1:10.0p1-7 fixed in 1:10.0p1-7+deb13u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56364 | LOW0.97 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-32710 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32710 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32710 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-42010 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-22770 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23876 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25897 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25968 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25971 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25983 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25986 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-22770 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23876 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25897 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25968 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25971 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25983 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25986 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-22770 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23876 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25897 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25968 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25971 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25983 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25986 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-22770 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23876 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25897 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25968 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25971 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25983 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25986 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-22770 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23876 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25897 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25968 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25971 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25983 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25986 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-22770 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23876 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-25897 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25968 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25971 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25983 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25986 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-34152 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 8.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-42217 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31789 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15467 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 47.6% High Exploitation Risk | Not Applicable |
| CVE-2026-6653 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23112 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49261 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2009-3546 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 10.2% High Exploitation Risk | Not Applicable |
| CVE-2026-58016 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33845 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-25898 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25987 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26284 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56367 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-25898 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25987 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26284 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56367 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-25898 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25987 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26284 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56367 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-25898 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25987 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26284 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56367 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-25898 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25987 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26284 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56367 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-25898 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25987 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26284 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56367 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56372 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44172 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42216 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7598 | NONE0 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44172 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-41142 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-9580 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9581 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-16376 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-2004 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-2005 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-2006 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6473 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-6637 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6638 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6477 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-10263 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42013 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5260 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25794 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56378 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25794 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56378 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25794 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56378 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25794 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56378 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25794 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56378 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25794 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56378 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6478 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc6-dev 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8286 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15079 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-28693 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28693 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28693 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28693 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28693 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28693 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25646 | NONE0 | libpng-dev 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u3 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-28387 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24882 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32775 | NONE0 | libexif-dev 0.6.25-1 fixed in 0.6.25-1+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25210 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25966 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30883 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30929 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30931 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56370 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25966 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30883 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30929 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30931 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56370 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25966 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30883 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30929 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30931 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56370 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25966 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30883 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30929 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30931 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56370 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25966 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30883 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30929 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30931 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56370 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25966 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30883 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30929 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30931 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56370 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-12495 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12839 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12840 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27622 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34588 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-22801 | NONE0 | libpng-dev 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4775 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 fixed in 4.7.0-3+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-8176 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8177 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22069 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38627 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68817 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71071 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71075 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71086 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71099 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71100 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71122 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71123 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71143 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71156 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71157 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71162 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71220 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71234 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23001 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23010 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23013 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23025 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23073 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23074 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23083 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23098 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23156 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23158 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23193 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23209 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23216 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23223 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23224 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23231 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-23233 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23354 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23387 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23390 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23408 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23410 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23411 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23412 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23413 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23422 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23427 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 96.3% Actively Exploited | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31474 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31506 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31530 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31566 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31582 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31730 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31731 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31787 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43007 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43059 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43120 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43128 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43138 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43178 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43260 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 93.2% Actively Exploited | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 92.8% Actively Exploited | Not Applicable |
| CVE-2026-45837 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45853 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45882 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45914 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45938 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45989 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45998 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46001 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46084 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46121 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46162 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46246 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53233 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53234 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33636 | NONE0 | libpng-dev 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-40355 | NONE0 | krb5-multidev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | krb5-multidev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | krb5-multidev 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-12064 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-5773 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6276 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8927 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-8932 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9079 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-9545 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45186 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5201 | NONE0 | libgdk-pixbuf-2.0-dev 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-58011 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33846 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-42009 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-40355 | NONE0 | libkrb5-dev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40356 | NONE0 | libkrb5-dev 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-5709 | NONE0 | libkrb5-dev 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-41254 | NONE0 | liblcms2-dev 2.16-2 fixed in 2.16-2+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2015-3276 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Not Applicable |
| CVE-2017-17740 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-23952 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25795 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25796 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25798 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25799 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25965 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25967 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25969 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25970 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25985 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25988 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26066 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26283 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28691 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32636 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33900 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33901 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33908 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49218 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53460 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53461 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56368 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-24485 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25989 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23952 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25795 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25796 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25798 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25799 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25965 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25967 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25969 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25970 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25985 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25988 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26066 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26283 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28691 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32636 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33900 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33901 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33908 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49218 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53460 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53461 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56368 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-24485 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25989 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23952 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25795 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25796 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25798 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25799 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25965 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25967 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25969 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25970 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25985 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25988 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26066 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26283 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28691 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32636 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33900 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33901 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33908 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49218 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53460 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53461 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56368 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-24485 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25989 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23952 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25795 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25796 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25798 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25799 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25965 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25967 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25969 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25970 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25985 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25988 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26066 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26283 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28691 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32636 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33900 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33901 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33908 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49218 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53460 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53461 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56368 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-24485 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25989 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23952 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25795 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25796 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25798 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25799 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25965 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25967 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25969 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25970 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25985 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25988 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26066 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26283 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28691 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32636 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33900 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33901 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33908 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49218 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53460 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53461 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56368 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-24485 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25989 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23952 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25795 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25796 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25798 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25799 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25965 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25967 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25969 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25970 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25985 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25988 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26066 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26283 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28691 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32636 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33900 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-33901 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33908 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45031 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45664 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46520 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46522 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-46523 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49218 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53460 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53461 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56368 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-61857 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61861 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-61870 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-24485 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25989 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-27135 | NONE0 | libnghttp2-dev 1.64.0-1.1 fixed in 1.64.0-1.1+deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-64181 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34543 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-9113 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2016-9114 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-33416 | NONE0 | libpng-dev 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-6479 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69421 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28388 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-28389 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28390 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-16232 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 4.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-22998 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-9547 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3833 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42011 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69419 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-9080 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34544 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34545 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-12912 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61144 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68800 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48165 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-6476 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48163 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48165 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-40385 | NONE0 | libexif-dev 0.6.25-1 fixed in 0.6.25-1+deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40386 | NONE0 | libexif-dev 0.6.25-1 fixed in 0.6.25-1+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42012 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27798 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33905 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56361 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28494 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27798 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33905 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56361 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28494 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27798 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33905 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56361 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28494 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27798 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33905 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56361 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28494 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27798 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33905 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56361 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28494 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27798 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33905 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45359 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56361 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56374 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28494 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34379 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40244 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-40250 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22695 | NONE0 | libpng-dev 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71101 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71116 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71136 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71231 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22984 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23187 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23244 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23325 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23363 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31430 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45851 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46094 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46140 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68357 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68811 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31786 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43056 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43330 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46155 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-71203 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45898 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45972 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46145 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46152 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46166 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46176 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52951 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52976 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53202 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53203 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53360 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31772 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43023 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43332 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45861 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45910 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46076 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46114 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46251 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52933 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52945 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53031 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53110 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53192 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53193 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53235 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53260 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53341 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56403 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56404 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56405 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56406 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56410 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56411 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13034 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1965 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14819 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-22185 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28686 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28686 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28686 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28686 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28686 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28686 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3996 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6475 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53094 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | libc6-dev 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-18064 | NONE0 | libcairo2-dev 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-11856 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-3784 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5545 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6429 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8924 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-14524 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2017-9937 | NONE0 | libjbig-dev 2.1-6.1+b2 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-25982 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28493 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28690 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53463 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53466 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-25982 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28493 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28690 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53463 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53466 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-25982 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28493 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28690 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53463 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53466 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-25982 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28493 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28690 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53463 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53466 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-25982 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28493 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28690 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53463 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53466 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-25982 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28493 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28690 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53463 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53466 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56366 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61465 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2017-11754 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-11755 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2018-15607 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 5.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-34303 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35549 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34303 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35549 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39329 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2016-10505 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9115 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2016-9116 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2016-9117 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-6988 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2023-37769 | NONE0 | libpixman-1-dev 0.44.0-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2673 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-10126 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1210 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23179 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31470 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-34303 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35549 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23178 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31525 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53081 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53085 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53092 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3805 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-28689 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28689 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28689 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28689 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28689 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28689 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46559 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13757 | NONE0 | libp11-kit-dev 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1757 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40147 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30937 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55628 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30937 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55628 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30937 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55628 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30937 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55628 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30937 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55628 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30937 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55628 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11187 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68770 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68819 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31511 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43044 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47166 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | krb5-multidev 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | krb5-multidev 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc6-dev 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-10966 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-50219 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56412 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-26458 | NONE0 | libkrb5-dev 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-26461 | NONE0 | libkrb5-dev 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48994 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55577 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48994 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55577 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48994 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55577 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48994 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55577 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48994 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55577 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46692 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48994 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55577 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31790 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-15468 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-66199 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69420 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-22796 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13151 | NONE0 | libtasn1-6-dev 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-0990 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-23246 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52908 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3783 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-7475 | NONE0 | libcairo2-dev 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32776 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32777 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32778 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23874 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25576 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30935 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30936 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31853 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33535 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33902 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34238 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40169 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40183 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40310 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40311 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40312 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42050 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48724 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48734 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55597 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56379 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23874 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25576 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30935 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30936 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31853 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33535 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33902 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34238 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40169 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40183 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40310 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40311 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40312 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42050 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48724 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48734 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55597 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56379 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23874 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25576 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30935 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30936 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31853 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33535 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33902 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34238 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40169 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40183 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40310 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40311 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40312 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42050 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48724 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48734 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55597 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56379 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23874 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25576 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30935 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30936 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31853 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33535 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33902 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34238 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40169 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40183 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40310 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40311 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40312 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42050 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48724 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48734 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55597 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56379 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23874 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25576 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30935 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30936 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31853 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33535 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33902 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34238 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40169 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40183 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40310 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40311 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40312 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42050 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48724 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48734 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55597 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56379 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23874 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25576 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-30935 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30936 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31853 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33535 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33902 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34238 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40169 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40183 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40310 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40311 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40312 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42050 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46521 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48724 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48734 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55597 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56379 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-0406 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-8678 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2017-7275 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-46557 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-48074 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-14988 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-39328 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng-dev 1.6.48-1+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15469 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22795 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61143 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-10911 | NONE0 | libxslt1-dev 1.1.35-1.2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21709 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21807 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22111 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22116 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22117 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39872 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68351 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68365 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68774 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68784 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68821 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68823 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71072 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71076 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71079 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71080 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71084 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71085 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71088 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71102 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71105 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71107 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71114 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71119 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71120 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71126 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71130 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71134 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71135 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71144 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71146 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71150 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71151 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71153 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71163 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71180 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71185 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71186 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71189 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71190 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71191 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71200 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71222 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71239 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71270 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71286 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71288 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71294 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71300 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71311 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71314 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22981 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22982 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22985 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22989 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22990 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22993 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22994 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22999 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23002 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23005 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23006 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23020 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23023 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23026 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23057 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23059 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23060 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23062 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23063 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23064 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23065 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23070 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23072 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23075 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23080 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23087 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23090 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23091 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23093 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23094 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23095 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23096 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23097 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23104 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23105 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23107 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23116 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23121 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23123 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23124 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23129 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23131 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23135 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23136 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23139 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23140 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23142 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23144 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23145 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23146 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23148 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23150 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23151 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23159 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23160 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23163 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23166 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23168 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23170 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23172 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23173 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23177 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23188 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23189 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23198 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23199 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23200 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23201 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23205 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23206 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23215 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23219 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23230 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23249 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23250 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23251 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23252 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23254 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23256 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23257 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23258 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23260 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23261 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23297 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23306 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23308 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23313 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23316 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23321 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23360 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23369 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23373 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23375 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23380 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23386 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23403 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23404 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23405 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23409 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23417 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23445 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23461 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23464 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23466 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23470 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31406 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31429 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31434 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31436 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31438 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31439 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31440 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31482 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31499 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31528 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31542 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31554 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31556 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31559 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31561 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31575 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31593 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31604 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31638 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31639 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31645 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31646 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31647 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31666 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31689 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31693 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31714 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31732 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31733 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31736 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31739 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31740 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31741 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31765 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31774 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43012 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43019 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43057 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43063 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43081 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43082 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43086 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43090 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43092 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43108 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43169 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43175 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43177 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43189 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43199 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43210 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43221 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43229 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43252 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43293 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43297 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43300 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43319 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43320 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43345 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43354 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43360 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43372 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43374 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43392 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43393 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43394 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43395 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43397 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43403 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43408 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43412 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43444 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43455 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43457 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43467 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43470 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43471 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43482 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43486 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43487 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43488 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45863 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45874 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45880 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45884 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45888 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45895 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45900 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45913 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45921 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45922 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45925 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45928 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45947 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45950 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45962 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45973 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45976 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46007 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46016 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46034 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46041 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46048 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46061 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46063 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46073 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46074 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46089 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46093 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46106 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46115 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46126 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46131 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46138 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46139 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46144 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46165 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46188 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46207 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46216 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46255 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46260 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46261 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46262 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46283 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46286 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46287 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46289 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46313 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46329 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52904 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52928 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52964 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52967 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52980 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52996 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53013 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53014 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53032 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53038 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53052 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53084 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53101 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53105 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53140 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53144 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53151 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53152 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53154 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53180 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53190 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53191 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53205 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53210 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53214 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53241 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53251 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53261 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53271 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53279 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53288 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53293 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53298 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53318 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | — | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68792 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71194 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45933 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46201 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46327 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52974 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53051 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53058 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53123 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53126 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53347 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | girepository-tools 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1489 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6472 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc6-dev 2.41-12+deb13u1 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc6-dev 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-4873 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6253 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7168 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-59375 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-23865 | NONE0 | libfreetype-dev 2.13.3+dfsg-1 fixed in 2.13.3+dfsg-1+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14831 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42015 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-22693 | NONE0 | libharfbuzz-dev 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34743 | NONE0 | liblzma-dev 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24484 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25637 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25638 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25797 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26983 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28687 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28688 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32259 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33899 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53467 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55594 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56365 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56371 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24484 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25637 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25638 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25797 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26983 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28687 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28688 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32259 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33899 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53467 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55594 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56365 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56371 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24484 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25637 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25638 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25797 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26983 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28687 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28688 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32259 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33899 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53467 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55594 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56365 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56371 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24484 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25637 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25638 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25797 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26983 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28687 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28688 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32259 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33899 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53467 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55594 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56365 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56371 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24484 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25637 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25638 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25797 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26983 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28687 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28688 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32259 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33899 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53467 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55594 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56365 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56371 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24484 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25637 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25638 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-25797 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26983 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28687 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28688 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32259 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33899 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45358 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53467 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55594 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56365 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56371 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56373 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-61858 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | — | Not Applicable |
| CVE-2025-55160 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34380 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng-dev 1.6.48-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2015-9019 | NONE0 | libxslt1-dev 1.1.35-1.2+deb13u2 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23053 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53194 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44173 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42326 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | girepository-tools 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-11850 | NONE0 | krb5-multidev 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-dev 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-11850 | NONE0 | libkrb5-dev 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-3134 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-34589 | NONE0 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61145 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-3477 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 4.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-23180 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-8926 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-14017 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28692 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28692 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28692 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28692 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28692 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28692 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u7 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-10536 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-15224 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-14159 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-33536 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55595 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33536 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55595 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33536 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55595 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33536 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55595 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33536 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55595 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-33536 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55595 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68160 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68749 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22986 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23161 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23167 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23210 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23440 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23441 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31456 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43415 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46194 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | uuid-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27799 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27799 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27799 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27799 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27799 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27799 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45624 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46693 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34757 | NONE0 | libpng-dev 1.6.48-1+deb13u1 fixed in 1.6.48-1+deb13u5 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23032 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31401 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2011-3389 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 No fix yet | 73.3% Actively Exploited | Not Applicable |
| CVE-2026-3494 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev 1:11.8.3-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3494 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev-compat 1:11.8.3-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-39327 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2003 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.8-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6474 | NONE0 | libpq-dev 17.7-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-dev 3.46.1-7 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2007-3476 | NONE0 | libwmf-dev 0.2.13-1.1+b3 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3494 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 fixed in 1:11.8.6-0+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:11.8.3-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | girepository-tools 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1484 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-15719 | NONE0 | libldap-dev 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49219 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49219 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49219 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49219 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49219 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56362 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49219 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.41-12+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-4438 | NONE0 | libc6-dev 2.41-12+deb13u1 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-47165 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u9 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69418 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | girepository-tools 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-41080 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0988 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3832 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-5419 | NONE0 | libgnutls28-dev 3.8.9-3+deb13u1 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl-dev 3.5.4-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0989 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-50422 | NONE0 | libcairo2-dev 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53464 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56363 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56376 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56377 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53464 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56363 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56376 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56377 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53464 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56363 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56376 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56377 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53464 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56363 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56376 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56377 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53464 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56363 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56376 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56377 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53464 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56363 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56376 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56377 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6192 | NONE0 | libopenjp2-7-dev 2.5.3-2.1~deb13u1 fixed in 2.5.3-2.1~deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-dev 3.46.1-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8732 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68775 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71148 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22978 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11731 | NONE0 | libxslt1-dev 1.1.35-1.2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-0992 | NONE0 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | girepository-tools 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-1485 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-24515 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8534 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56364 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56364 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56364 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56364 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56364 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56364 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b7 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.22.21 fixed in 1.22.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg-dev 1.22.21 fixed in 1.22.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24481 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-49295 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49337 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49346 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45382 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | — | Not Applicable |
| CVE-2026-45383 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | — | Not Applicable |
| CVE-2026-54240 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | — | Not Applicable |
| CVE-2026-54241 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | — | Not Applicable |
| CVE-2026-2219 | NONE0 | libdpkg-perl 1.22.21 fixed in 1.22.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50811 | NONE0 | libfreetype-dev 2.13.3+dfsg-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50811 | NONE0 | libfreetype6 2.13.3+dfsg-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-2+b1 fixed in 1.3.14-2+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-dev 1.3.14-2+b1 fixed in 1.3.14-2+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47254 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-50142 | NONE0 | libheif-plugin-dav1d 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47251 | 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 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47254 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-50142 | NONE0 | libheif-plugin-libde265 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47251 | 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 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47254 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47709 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-50142 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-47251 | NONE0 | libheif1 1.19.8-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-42798 | NONE0 | liblcms2-2 2.16-2 fixed in 2.16-2+deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-42798 | NONE0 | liblcms2-dev 2.16-2 fixed in 2.16-2+deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.16-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-24481 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u6 | 0.3% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u4 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.64.0-1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-dev 1.64.0-1.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.46.1-7 fixed in 3.46.1-7+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-dev 3.46.1-7 fixed in 3.46.1-7+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.46.1-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.46.1-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-dev 3.46.1-7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-dev 3.46.1-7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff-dev 4.7.0-3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiffxx6 4.7.0-3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| 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-43011 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31558 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31718 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31743 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43376 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43379 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40276 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68810 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71140 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23055 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43307 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46036 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46085 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46326 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53328 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53336 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53346 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31644 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43438 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46263 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46288 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46332 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53097 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53098 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53119 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.12.63-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.63-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13-minimal 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | uuid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | uuid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | uuid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | uuid-dev 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-58469 | NONE0 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-47242 | NONE0 | net-imap 0.3.9 fixed in ~> 0.5.15, >= 0.6.4.1 | 0.1% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.