Last scanned:
This base/runtime image ships critical vulnerabilities that any image built on it would inherit; they must be remediated before the final image goes to production. An attacker with network access could exploit CVE-2026-56372 to leak sensitive information or cause denial of service, with no privileges or user interaction required. The image includes a large number of vulnerabilities (2,590 total) due to packages like ImageMagick, and post-exploit issues such as CVE-2019-1010022 could escalate attacks if a prior foothold is gained. Immediate remediation—such as updating ImageMagick or removing it if unused—is non-negotiable before any production use. 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 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | CRITICAL9.1 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-13221 | CRITICAL9.1 | perl-modules-5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | perl 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-49261 | HIGH8.33 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-49261 | HIGH8.33 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-49261 | HIGH8.33 | libmariadb3 1:11.8.6-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-42217 | HIGH8.33 | libopenexr-dev 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-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-6653 | HIGH8.33 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | perl 5.40.1-6 No fix yet | 0.4% 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-2008-4609 | HIGH8.16 | linux-libc-dev 6.12.90-2 No fix yet | 32.1% High Exploitation Risk | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.12.90-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19449 | HIGH7.8 | linux-libc-dev 6.12.90-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 6.12.90-2 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-64600 | HIGH7.8 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 6.12.90-2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 6.12.90-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56367 | HIGH7.73 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH7.73 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH7.73 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH7.73 | libmariadb3 1:11.8.6-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-42216 | HIGH7.73 | libopenexr-dev 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-42496 | HIGH7.73 | perl 5.40.1-6 No fix yet | 0.4% 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-2018-5709 | HIGH7.5 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-dev 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-dev 2.6.10+dfsg-1 No fix yet | 7.0% 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-61857 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61857 | HIGH7.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61861 | HIGH7.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61863 | HIGH7.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61866 | HIGH7.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61870 | HIGH7.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40691 | HIGH7.5 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.12.90-2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.12.90-2 No fix yet | 1.2% 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-41142 | HIGH7.48 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | HIGH7.28 | libperl5.40 5.40.1-6 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13221 | HIGH7.28 | perl 5.40.1-6 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13221 | HIGH7.28 | perl-base 5.40.1-6 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2025-10263 | HIGH7.14 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53398 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53399 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-63794 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63795 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63797 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63824 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63829 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63830 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63831 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63875 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63884 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63886 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63887 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63888 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63899 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63917 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63921 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63922 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63924 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63939 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63952 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63956 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63962 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63970 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63993 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63994 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64007 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64009 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64017 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64018 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64026 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64051 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64061 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64099 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64113 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64132 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64137 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64191 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53366 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53381 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53384 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53388 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53391 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53392 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-53393 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53397 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63800 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63801 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63802 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63807 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63808 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63809 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63823 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63826 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63883 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63889 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63891 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63894 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63896 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63898 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63901 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63912 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63913 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63914 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63916 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63918 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63919 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63920 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63925 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63928 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63938 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63940 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63941 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63944 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63945 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63946 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63947 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63957 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63958 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63971 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63975 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63978 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63979 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63984 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63987 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63992 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63996 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64000 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64001 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64002 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64011 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64015 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64024 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64025 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64029 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64032 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64034 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64047 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64048 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64053 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64068 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64098 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64102 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64109 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64111 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64114 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64115 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64117 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64119 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64136 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64160 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64174 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64189 | HIGH7 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-64192 | HIGH7 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56378 | MEDIUM6.97 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% 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-44168 | MEDIUM6.8 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM6.8 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM6.8 | libmariadb3 1:11.8.6-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 | libwmf-dev 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-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-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1-dev 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-56370 | MEDIUM6.63 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56370 | MEDIUM6.63 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb3 1:11.8.6-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-2025-12495 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-dev 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-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-2025-8176 | MEDIUM6.63 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.3% 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-11979 | MEDIUM6.63 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22069 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53097 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53098 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53233 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53234 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | perl 5.40.1-6 No fix yet | 0.3% 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-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-18064 | MEDIUM6.5 | libcairo2-dev 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 | libjbig-dev 2.1-6.1+b2 No fix yet | 2.8% 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-56366 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56366 | MEDIUM6.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61465 | MEDIUM6.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 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 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.12.90-2 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% 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-45186 | MEDIUM6.38 | libexpat1-dev 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-dev-bin 2.84.4-3~deb13u3 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-49218 | MEDIUM6.38 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56368 | MEDIUM6.38 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% 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-2025-64181 | MEDIUM6.38 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-dev 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-7210 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.8% 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-2026-53266 | MEDIUM6.38 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | perl 5.40.1-6 No fix yet | 0.4% 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-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-34544 | MEDIUM6.21 | libopenexr-dev 3.1.13-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-dev 3.1.13-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff-dev 4.7.0-3+deb13u2 fixed in 4.7.0-3+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u2 fixed in 4.7.0-3+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiffxx6 4.7.0-3+deb13u2 fixed in 4.7.0-3+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.0% 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-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-56361 | MEDIUM6.03 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56361 | MEDIUM6.03 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56374 | MEDIUM6.03 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% 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-34379 | MEDIUM6.03 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-dev 3.1.13-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.3% 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-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53346 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46316 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52951 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52976 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53202 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53203 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53277 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53360 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53031 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53110 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53182 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53192 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53193 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53209 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53235 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53260 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53341 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | 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+deb13u1 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+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5+deb13u1 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-2025-13151 | MEDIUM5.9 | libtasn1-6-dev 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.90-2 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.12.90-2 No fix yet | 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-56132 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-dev 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53094 | MEDIUM5.7 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-dane0t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls-openssl27t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls28-dev 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u3 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-53463 | MEDIUM5.52 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53466 | MEDIUM5.52 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 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-2023-37769 | MEDIUM5.52 | libpixman-1-dev 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+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2+deb13u2 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+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2+deb13u2 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-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.90-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | perl 5.40.1-6 No fix yet | 0.1% 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-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-7475 | MEDIUM5.5 | libcairo2-dev 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+deb13u9 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+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 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-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53365 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-53394 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53400 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53402 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2026-63803 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63804 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63822 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63832 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63838 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63842 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63850 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63852 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63858 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63860 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63865 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63867 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63868 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63870 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63890 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63892 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63893 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63897 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63900 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63902 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63903 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63904 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63906 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63926 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63927 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63937 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63942 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63943 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63948 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63961 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63963 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63968 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63969 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63976 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63980 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63983 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63985 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63995 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64004 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64005 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64006 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64012 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64014 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64036 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64038 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64046 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64052 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64058 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64059 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64063 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64064 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64065 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64067 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64073 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64076 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64077 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64079 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64103 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64106 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64112 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64116 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64118 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64121 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64123 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64125 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64126 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64127 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64128 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64133 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64157 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64159 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64170 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64173 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64177 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64178 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64185 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64190 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64205 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64206 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-53385 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-53403 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63810 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63821 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Directly Exposed |
| CVE-2026-63843 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63844 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63845 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63851 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63853 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63869 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63871 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63872 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63876 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63877 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63929 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63964 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63973 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63974 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63990 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63991 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63997 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-63998 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-63999 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64003 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64039 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64060 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64062 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64066 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64070 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64078 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64105 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64131 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64134 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64144 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64146 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 No fix yet | — | Directly Exposed |
| CVE-2026-64153 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64155 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64158 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64163 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64179 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64180 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64182 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64183 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64184 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Directly Exposed |
| CVE-2026-64187 | MEDIUM5.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53081 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53085 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53092 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% 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-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 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-2025-59375 | MEDIUM5.3 | libexpat1-dev 2.7.1-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56373 | MEDIUM5.3 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61858 | MEDIUM5.3 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit-dev 0.25.5-3 No fix yet | 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-1757 | MEDIUM5.27 | 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 | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% 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 | libblkid-dev 2.41-5 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-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55628 | MEDIUM5.18 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount-dev 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 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-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% 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-2026-50219 | MEDIUM5.02 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1-dev 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+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55577 | MEDIUM5.02 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u2 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+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% 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-0990 | MEDIUM5.02 | 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 | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev-bin 2.84.4-3~deb13u3 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+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 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 | libwmf-dev 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-2010-4563 | MEDIUM5 | linux-libc-dev 6.12.90-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-52908 | MEDIUM4.93 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| 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-1010022 | MEDIUM4.7 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2019-1010022 | MEDIUM4.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2019-1010022 | MEDIUM4.7 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2019-1010022 | MEDIUM4.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.12.90-2 No fix yet | 1.4% Low-Moderate Risk | 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 | libblkid-dev 2.41-5 No fix yet | 0.4% 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-66382 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-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-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48724 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55597 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount-dev 2.41-5 No fix yet | 0.4% 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-2025-48074 | MEDIUM4.67 | libopenexr-dev 3.1.13-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14988 | MEDIUM4.67 | libopenexr-dev 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~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2+deb13u2 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-61143 | MEDIUM4.67 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1-dev 1.1.35-1.2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31435 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31562 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31732 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43272 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43325 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43326 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43331 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43337 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43346 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43485 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46096 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46216 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46256 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52941 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52964 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52967 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52980 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52996 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53013 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53014 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53032 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53038 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53051 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53052 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53058 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53084 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53101 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53105 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53140 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53142 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53144 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53151 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53152 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53154 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53180 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53183 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53184 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53190 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53191 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53205 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53210 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53214 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53241 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53251 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53261 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53271 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53274 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53279 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53288 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53293 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53298 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53318 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53321 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53347 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53350 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52974 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53123 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53126 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% 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-27171 | MEDIUM4.67 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | MEDIUM4.64 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56367 | MEDIUM4.64 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56367 | MEDIUM4.64 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56367 | MEDIUM4.64 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | MEDIUM4.64 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% 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-58055 | MEDIUM4.59 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-dev 1.64.0-1.1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u3 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-61857 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61861 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61863 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61866 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61870 | MEDIUM4.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61857 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61861 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61863 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61866 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61870 | MEDIUM4.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61857 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61861 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61863 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61866 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61870 | MEDIUM4.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u3 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-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-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid-dev 2.41-5 No fix yet | 0.4% 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-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-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma-dev 5.8.1-1 fixed in 5.8.1-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-53467 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53467 | MEDIUM4.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55594 | MEDIUM4.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56365 | MEDIUM4.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56371 | MEDIUM4.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount-dev 2.41-5 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-34380 | MEDIUM4.5 | libopenexr-dev 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 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u2 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-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% 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-53194 | MEDIUM4.5 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | perl 5.40.1-6 No fix yet | 0.4% 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-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | MEDIUM4.39 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | MEDIUM4.39 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-dev 3.46.1-7+deb13u1 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 | libwmf-dev 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-2026-11850 | MEDIUM4.25 | krb5-multidev 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | 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-42250 | MEDIUM4.25 | libbz2-dev 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 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+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssrpc4t64 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5clnt-mit12 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5srv-mit12 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkdb5-10t64 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-dev 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5+deb13u1 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-34589 | MEDIUM4.25 | libopenexr-dev 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-2025-61145 | MEDIUM4.25 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | perl 5.40.1-6 No fix yet | 0.3% 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-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| 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 | libldap-dev 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.18 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | MEDIUM4.18 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | MEDIUM4.18 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56378 | MEDIUM4.18 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56378 | MEDIUM4.18 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56378 | MEDIUM4.18 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | MEDIUM4.18 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | MEDIUM4.18 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | MEDIUM4.18 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-dev 2.6.10+dfsg-1 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-55595 | MEDIUM4 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55595 | MEDIUM4 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount-dev 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23469 | MEDIUM4 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u3 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+b3 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+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW3.98 | gpgsm 2.4.7-21+deb13u1+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56370 | LOW3.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56370 | LOW3.98 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56370 | LOW3.98 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| 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+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56366 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61465 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2017-11754 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11755 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15607 | LOW3.9 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56366 | LOW3.9 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61465 | LOW3.9 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2017-11754 | LOW3.9 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11755 | LOW3.9 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15607 | LOW3.9 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56366 | LOW3.9 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61465 | LOW3.9 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2017-11754 | LOW3.9 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11755 | LOW3.9 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15607 | LOW3.9 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-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 | libwmf-dev 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+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW3.82 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW3.82 | girepository-tools 2.84.4-3~deb13u3 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-49218 | LOW3.82 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-49218 | LOW3.82 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53460 | LOW3.82 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53461 | LOW3.82 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56368 | LOW3.82 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-49218 | LOW3.82 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53460 | LOW3.82 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53461 | LOW3.82 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56368 | LOW3.82 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW3.82 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW3.82 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 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+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-60000 | LOW3.82 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW3.82 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u3 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-2026-61860 | LOW3.7 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61860 | LOW3.7 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61868 | LOW3.7 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61871 | LOW3.7 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44169 | LOW3.65 | libmariadb-dev 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb-dev-compat 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7-dev 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.90-2 No fix yet | 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-56361 | LOW3.62 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56361 | LOW3.62 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56374 | LOW3.62 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56361 | LOW3.62 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56374 | LOW3.62 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.3% 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-56362 | LOW3.57 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56362 | LOW3.57 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% 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+deb13u4 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15146 | LOW3.54 | wget 1.25.0-2 No fix yet | — | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 8.0% 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-2019-16089 | LOW3.48 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | 0.3% 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+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW3.31 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW3.31 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53466 | LOW3.31 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53463 | LOW3.31 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53466 | LOW3.31 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1-dev 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.3% 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-59998 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-60001 | LOW3.31 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.13 3.13.5-2+deb13u2 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+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-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+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7275 | LOW3.3 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8678 | LOW3.3 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7275 | LOW3.3 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2016-8678 | LOW3.3 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7275 | LOW3.3 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56375 | LOW3.3 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56375 | LOW3.3 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61859 | LOW3.3 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-56372 | LOW3.28 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56372 | LOW3.28 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56372 | LOW3.28 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56373 | LOW3.18 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61858 | LOW3.18 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56373 | LOW3.18 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61858 | LOW3.18 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56373 | LOW3.18 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61858 | LOW3.18 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-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-41080 | LOW3.15 | libexpat1-dev 2.7.1-2 No fix yet | 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-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-0989 | LOW3.15 | 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 | 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-55628 | LOW3.11 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55628 | LOW3.11 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55628 | LOW3.11 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 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-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+deb13u4 No fix yet | 13.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48994 | LOW3.01 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48994 | LOW3.01 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55577 | LOW3.01 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48994 | LOW3.01 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55577 | LOW3.01 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.13 3.13.5-2+deb13u2 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+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW3 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | 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+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3134 | LOW3 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2012-0039 | LOW3 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-61862 | LOW2.9 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61862 | LOW2.9 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61864 | LOW2.9 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61865 | LOW2.9 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61867 | LOW2.9 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61869 | LOW2.9 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60002 | LOW2.87 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-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-2019-6110 | LOW2.81 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 20.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-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-48724 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48724 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48734 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55597 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48724 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48734 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55597 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-0406 | LOW2.8 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.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-2026-0864 | LOW2.8 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13-minimal 3.13.5-2+deb13u2 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-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-50422 | LOW2.8 | libcairo2-dev 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53464 | LOW2.8 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56363 | LOW2.8 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56376 | LOW2.8 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56377 | LOW2.8 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% 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-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.2% 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+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-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-2025-8732 | LOW2.8 | 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 | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | perl 5.40.1-6 No fix yet | 0.5% 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+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59996 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59997 | LOW2.75 | openssh-client 1:10.0p1-7+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-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+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53467 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53467 | LOW2.7 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55594 | LOW2.7 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56365 | LOW2.7 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56371 | LOW2.7 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53467 | LOW2.7 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55594 | LOW2.7 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56365 | LOW2.7 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56371 | LOW2.7 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-55160 | LOW2.7 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4-openssl-dev 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 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-12781 | LOW2.7 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u2 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-dev 1.1.35-1.2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:10.0p1-7+deb13u4 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-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-61872 | LOW2.5 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| CVE-2026-61872 | LOW2.5 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Directly Exposed |
| 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-0992 | LOW2.46 | 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 | Directly Exposed |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55595 | LOW2.4 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55595 | LOW2.4 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55595 | LOW2.4 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u3 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-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.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-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-2026-1502 | LOW2.29 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.13-minimal 3.13.5-2+deb13u2 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-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-61860 | LOW2.22 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61868 | LOW2.22 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61871 | LOW2.22 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61860 | LOW2.22 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61868 | LOW2.22 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61871 | LOW2.22 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61860 | LOW2.22 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61868 | LOW2.22 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61871 | LOW2.22 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56362 | LOW2.14 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-49219 | LOW2.14 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56362 | LOW2.14 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-49219 | LOW2.14 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56362 | LOW2.14 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-49219 | LOW2.14 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 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-2026-24515 | LOW2.12 | libexpat1-dev 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56375 | LOW1.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61859 | LOW1.98 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56375 | LOW1.98 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61859 | LOW1.98 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-56375 | LOW1.98 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61859 | LOW1.98 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | 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-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61862 | LOW1.74 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61864 | LOW1.74 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61865 | LOW1.74 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61867 | LOW1.74 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61869 | LOW1.74 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61862 | LOW1.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61864 | LOW1.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61865 | LOW1.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61867 | LOW1.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61869 | LOW1.74 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61862 | LOW1.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61864 | LOW1.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61865 | LOW1.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61867 | LOW1.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61869 | LOW1.74 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | 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+b3 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+b3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.4.7-21+deb13u1+b3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53464 | LOW1.68 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53464 | LOW1.68 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56363 | LOW1.68 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56376 | LOW1.68 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56377 | LOW1.68 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53464 | LOW1.68 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56363 | LOW1.68 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56376 | LOW1.68 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56377 | LOW1.68 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.2% 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 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56364 | LOW1.61 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 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-61872 | LOW1.5 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61872 | LOW1.5 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-61872 | LOW1.5 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | dirmngr 2.4.7-21+deb13u1+b3 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+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpg-agent 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgconf 2.4.7-21+deb13u1+b3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgsm 2.4.7-21+deb13u1+b3 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-56364 | LOW0.97 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56364 | LOW0.97 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56364 | LOW0.97 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u11 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-49261 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-44172 | NONE0 | mariadb-common 1:11.8.6-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-2026-44168 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-24882 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-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-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44171 | NONE0 | mariadb-common 1:11.8.6-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-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-48163 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48165 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.0% 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-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-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.6-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-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% 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 | 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-2026-44169 | NONE0 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% 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-2022-3219 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.3% 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-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% 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-2026-57062 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-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+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.10-4 No fix yet | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick-7-common 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick-7.q16 8:7.1.1.43+dfsg1-1+deb13u9 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+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4-openssl-dev 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% 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-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-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-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-2025-61147 | NONE0 | libde265-0 1.0.15-1+b3 No fix yet | 0.2% 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-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-2025-29070 | NONE0 | liblcms2-2 2.16-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.16-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7-arch-config 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7.q16-10-extra 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-7-headers 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-7.q16-10 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-7.q16-dev 8:7.1.1.43+dfsg1-1+deb13u9 fixed in 8:7.1.1.43+dfsg1-1+deb13u10 | — | Not Applicable |
| CVE-2026-61464 | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-dev 8:7.1.1.43+dfsg1-1+deb13u9 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-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | 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+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u2 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-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff-dev 4.7.0-3+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiffxx6 4.7.0-3+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-14586 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-32665 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-41637 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-42955 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-44621 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-44687 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-44690 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-46582 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-50045 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-50046 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-50243 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-50248 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-50251 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-50252 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-52863 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-54478 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-55708 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-55717 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-55973 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-55990 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-55991 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-56416 | NONE0 | libunbound8 1.22.0-2+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-56444 | NONE0 | libunbound8 1.22.0-2+deb13u3 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-43185 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53328 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53336 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.96-1 | — | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63936 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64141 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64142 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64169 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | — | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53119 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.90-2 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-57433 | NONE0 | perl 5.40.1-6 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-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | 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+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13 3.13.5-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-minimal 3.13.5-2+deb13u2 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 |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.