Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who reaches the packaged libraries could execute arbitrary code inside the container or cause denial of service, with CVE-2019-16227 (liblmdb0, severity 9.8) and the glibc issue CVE-2019-1010023 (severity 8.8) being the most impactful findings. Several of the severe items have narrow preconditions: CVE-2019-16227 requires accessing a data.mdb file supplied by the attacker, CVE-2019-1010023 requires running ldd against a malicious ELF, and the libperl regex overflow only applies to 32-bit perl builds. The 334 post-exploit-only findings are all below severity 6.0 (max 4.64), so they are secondary to the exposed surface. Restricting inbound network access to the container and avoiding untrusted file or XML input would remove the practical paths to the highest-severity exposed findings.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-16227 | CRITICAL9.8 | liblmdb0 0.9.31-1+b2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.43-3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-gconv-modules-extra 2.43-3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.43-3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2014-8166 | HIGH8.8 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2009-4487 | HIGH7.82 | nginx 1.26.3-3+deb13u7 No fix yet | 29.5% High Exploitation Risk | Directly Exposed |
| CVE-2009-4487 | HIGH7.82 | nginx-common 1.26.3-3+deb13u7 No fix yet | 29.5% High Exploitation Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | HIGH7.73 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.43-3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.43-3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-gconv-modules-extra 2.43-3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-gconv-modules-extra 2.43-3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.43-3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.43-3 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.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libip4tc2 1.8.11-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libip6tc2 1.8.11-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.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-2019-16226 | HIGH7.5 | liblmdb0 0.9.31-1+b2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16228 | HIGH7.5 | liblmdb0 0.9.31-1+b2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7210 | HIGH7.5 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7210 | HIGH7.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18798 | HIGH7.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | HIGH7.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | HIGH7.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | HIGH7.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | HIGH7.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libxtables12 1.8.11-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0337 | HIGH7.5 | nginx 1.26.3-3+deb13u7 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0337 | HIGH7.5 | nginx-common 1.26.3-3+deb13u7 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18798 | HIGH7.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | HIGH7.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | HIGH7.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | HIGH7.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | HIGH7.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12247 | HIGH7.5 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12247 | HIGH7.5 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12247 | HIGH7.5 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12247 | HIGH7.5 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12247 | HIGH7.5 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd-shared 261.2-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 261.2-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 261.2-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93834 | HIGH7.48 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93834 | HIGH7.48 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93834 | HIGH7.48 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93834 | HIGH7.48 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93834 | HIGH7.48 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-3872 | HIGH7.31 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3872 | HIGH7.31 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3872 | HIGH7.31 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3872 | HIGH7.31 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-3872 | HIGH7.31 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | HIGH7.22 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH7.14 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM6.97 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60005 | MEDIUM6.97 | nginx 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60005 | MEDIUM6.97 | nginx-common 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-81627 | MEDIUM6.97 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81627 | MEDIUM6.97 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81627 | MEDIUM6.97 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81627 | MEDIUM6.97 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-81627 | MEDIUM6.97 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39821 | MEDIUM6.97 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56858 | MEDIUM6.88 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libfdisk1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libblkid1 2.41.5-0+deb13u1 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-76957 | MEDIUM6.63 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libfdisk1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libfdisk1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | MEDIUM6.63 | libnss3 2:3.127-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | MEDIUM6.63 | libnss3 2:3.127-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | MEDIUM6.63 | libnss3 2:3.127-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | MEDIUM6.63 | libnss3 2:3.127-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM6.63 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | MEDIUM6.63 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-12003 | MEDIUM6.63 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86139 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-1386 | MEDIUM6.63 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1386 | MEDIUM6.63 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1386 | MEDIUM6.63 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1386 | MEDIUM6.63 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1386 | MEDIUM6.63 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39822 | MEDIUM6.63 | stdlib v1.25.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-14164 | MEDIUM6.38 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33630 | MEDIUM6.38 | libcares2 1.34.5-1+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-69184 | MEDIUM6.38 | libcares2 1.34.5-1+deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-69186 | MEDIUM6.38 | libcares2 1.34.5-1+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM6.38 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-66046 | MEDIUM6.38 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76956 | MEDIUM6.38 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM6.38 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM6.38 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM6.38 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM6.38 | libx11-6 2:1.8.13-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM6.38 | libx11-data 2:1.8.13-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM6.38 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM6.38 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-46603 | MEDIUM6.38 | golang.org/x/image v0.44.0 fixed in 0.45.0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-25679 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27145 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32280 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32281 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32283 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33811 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33814 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-33818 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39820 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-39836 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42499 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42504 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56853 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56859 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56860 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56862 | MEDIUM6.38 | stdlib v1.25.7 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM6.29 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95508 | MEDIUM6.29 | libslirp0 4.9.3-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12080 | MEDIUM6.21 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12080 | MEDIUM6.21 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12080 | MEDIUM6.21 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12080 | MEDIUM6.21 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12080 | MEDIUM6.21 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82049 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82049 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12928 | MEDIUM6 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 23.0% High Exploitation Risk | Directly Exposed |
| CVE-2019-12928 | MEDIUM6 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 23.0% High Exploitation Risk | Directly Exposed |
| CVE-2019-12928 | MEDIUM6 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 23.0% High Exploitation Risk | Directly Exposed |
| CVE-2019-12928 | MEDIUM6 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 23.0% High Exploitation Risk | Directly Exposed |
| CVE-2019-12928 | MEDIUM6 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 23.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-bin 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-bin 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55893 | MEDIUM5.95 | libcapstone5 5.0.9-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libfdisk1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42533 | MEDIUM5.95 | nginx 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42533 | MEDIUM5.95 | nginx-common 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.1% 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 | libk5crypto3 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 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12929 | MEDIUM5.88 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12929 | MEDIUM5.88 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12929 | MEDIUM5.88 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12929 | MEDIUM5.88 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-12929 | MEDIUM5.88 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-bin 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49263 | MEDIUM5.78 | libcapstone5 5.0.9-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | liblmdb0 0.9.31-1+b2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM5.7 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | MEDIUM5.52 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.52 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | MEDIUM5.52 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-17084 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-17084 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-85769 | MEDIUM5.52 | libtpms0 0.9.2-3.2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | MEDIUM5.52 | libx11-6 2:1.8.13-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | MEDIUM5.52 | libx11-data 2:1.8.13-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56434 | MEDIUM5.52 | nginx 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56434 | MEDIUM5.52 | nginx-common 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12067 | MEDIUM5.52 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-12067 | MEDIUM5.52 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-12067 | MEDIUM5.52 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-12067 | MEDIUM5.52 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-12067 | MEDIUM5.52 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39825 | MEDIUM5.52 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-32282 | MEDIUM5.44 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27447 | MEDIUM5.35 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.43-3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.43-3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-gconv-modules-extra 2.43-3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-gconv-modules-extra 2.43-3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.43-3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.43-3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49282 | MEDIUM5.27 | libcapstone5 5.0.9-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39314 | MEDIUM5.27 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | MEDIUM5.27 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | libldb2 2:2.11.0+samba4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | libtalloc2 2:2.4.3+samba4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | libtdb1 2:1.4.13+samba4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | libtevent0t64 2:0.16.2+samba4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | libwbclient0 2:4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM5.18 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | samba 2:4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | samba-common 2:4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | samba-common-bin 2:4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15779 | MEDIUM5.18 | samba-libs 2:4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75900 | MEDIUM5.18 | swtpm 0.7.1-1.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75900 | MEDIUM5.18 | swtpm-libs 0.7.1-1.5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32289 | MEDIUM5.18 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35503 | MEDIUM5.1 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35503 | MEDIUM5.1 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35503 | MEDIUM5.1 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35503 | MEDIUM5.1 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35503 | MEDIUM5.1 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12725 | MEDIUM5.02 | dnsmasq 2.91-1+deb13u1 fixed in 2.91-1+deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-12725 | MEDIUM5.02 | dnsmasq-base 2.91-1+deb13u1 fixed in 2.91-1+deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-bin 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-bin 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6 2.43-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-47143 | MEDIUM5.02 | libcapstone5 5.0.9-1 No fix yet | 0.5% 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 | libk5crypto3 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 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15534 | MEDIUM4.84 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87910 | MEDIUM4.84 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87910 | MEDIUM4.84 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55894 | MEDIUM4.67 | libcapstone5 5.0.9-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | MEDIUM4.67 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% 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.8.3-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libfdisk1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.58-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd-shared 261.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 261.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 261.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23679 | MEDIUM4.67 | libusb-1.0-0 2:1.0.30-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47104 | MEDIUM4.67 | libusb-1.0-0 2:1.0.30-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | MEDIUM4.67 | libx11-6 2:1.8.13-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | MEDIUM4.67 | libx11-data 2:1.8.13-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.67 | libxml2 2.12.7+dfsg+really2.9.14-2.1+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-2024-8354 | MEDIUM4.67 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-8354 | MEDIUM4.67 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-8354 | MEDIUM4.67 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-8354 | MEDIUM4.67 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-8354 | MEDIUM4.67 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.3% 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-32288 | MEDIUM4.67 | stdlib v1.25.7 fixed in 1.25.9, 1.26.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | MEDIUM4.64 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41079 | MEDIUM4.59 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27142 | MEDIUM4.59 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39823 | MEDIUM4.59 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-39826 | MEDIUM4.59 | stdlib v1.25.7 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2012-2663 | MEDIUM4.5 | iptables 1.8.11-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18798 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63072 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14457 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54874 | MEDIUM4.5 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-7210 | MEDIUM4.5 | python3.13 3.13.5-2+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-7210 | MEDIUM4.5 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12247 | MEDIUM4.5 | qemu-utils 1:11.1.0+ds-2 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12969 | MEDIUM4.5 | dnsmasq 2.91-1+deb13u1 fixed in 2.91-1+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12969 | MEDIUM4.5 | dnsmasq-base 2.91-1+deb13u1 fixed in 2.91-1+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8367 | MEDIUM4.5 | libaria2-0 1.37.0+debian-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-bin 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | MEDIUM4.5 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libfdisk1 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0t64 2.84.4-3~deb13u3 fixed in 2.84.4-3~deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM4.5 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.58-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15806 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15806 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-19672 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd-shared 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd-shared 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd-shared 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 261.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58058 | MEDIUM4.5 | github.com/ulikunitz/xz v0.5.14 fixed in 0.5.15 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42505 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42507 | MEDIUM4.5 | stdlib v1.25.7 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93834 | MEDIUM4.49 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | xxd 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | MEDIUM4.49 | xxd 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34990 | MEDIUM4.42 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38798 | MEDIUM4.42 | ovmf-generic 2026.05-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3872 | MEDIUM4.39 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | MEDIUM4.33 | libx11-6 2:1.8.13-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | MEDIUM4.33 | libx11-data 2:1.8.13-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95507 | MEDIUM4.3 | libslirp0 4.9.3-1 No fix yet | — | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.2% 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 | libk5crypto3 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 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-81627 | MEDIUM4.18 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | xxd 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | xxd 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.43-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48092 | MEDIUM4.13 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12928 | MEDIUM4.06 | qemu-utils 1:11.1.0+ds-2 No fix yet | 23.0% High Exploitation Risk | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | fdisk 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.43-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-gconv-modules-extra 2.43-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.43-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14266 | LOW3.98 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | fdisk 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | fdisk 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-25724 | LOW3.98 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW3.98 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-12003 | LOW3.98 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-1386 | LOW3.98 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-43961 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73072 | LOW3.98 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-47268 | LOW3.9 | iputils-ping 3:20240905-3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-14164 | LOW3.82 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW3.82 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-14456 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63075 | LOW3.82 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | xxd 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13002 | LOW3.74 | dnsmasq 2.91-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13002 | LOW3.74 | dnsmasq-base 2.91-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3735 | LOW3.74 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6426 | LOW3.74 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3735 | LOW3.74 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6426 | LOW3.74 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3735 | LOW3.74 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6426 | LOW3.74 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3735 | LOW3.74 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6426 | LOW3.74 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3735 | LOW3.74 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6426 | LOW3.74 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW3.72 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW3.72 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-12080 | LOW3.72 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | xxd 2:9.1.1230-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-73073 | LOW3.72 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73076 | LOW3.72 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-73077 | LOW3.72 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | xxd 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-87875 | LOW3.65 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48103 | LOW3.62 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48111 | LOW3.62 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82049 | LOW3.62 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82049 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58471 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW3.62 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-36648 | LOW3.6 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-36648 | LOW3.6 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-36648 | LOW3.6 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-36648 | LOW3.6 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-36648 | LOW3.6 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-36648 | LOW3.6 | qemu-utils 1:11.1.0+ds-2 No fix yet | 1.7% Low-Moderate Risk | 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-78409 | LOW3.57 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | fdisk 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | xxd 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW3.57 | libc-bin 2.43-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6 2.43-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.54 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.43-3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-gconv-modules-extra 2.43-3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.43-3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16224 | LOW3.53 | liblmdb0 0.9.31-1+b2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16225 | LOW3.53 | liblmdb0 0.9.31-1+b2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-12929 | LOW3.53 | qemu-utils 1:11.1.0+ds-2 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92382 | LOW3.48 | libusbredirparser1t64 0.15.0-1+b2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28419 | LOW3.37 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-58051 | LOW3.31 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW3.31 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.31 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-17084 | LOW3.31 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-17084 | LOW3.31 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-12067 | LOW3.31 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58469 | LOW3.31 | wget 1.25.0-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-16599 | LOW3.31 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-8612 | LOW3.23 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-8612 | LOW3.23 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-8612 | LOW3.23 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-8612 | LOW3.23 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-8612 | LOW3.23 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc-bin 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc-gconv-modules-extra 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6 2.43-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-35503 | LOW3.06 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.01 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-87910 | LOW2.91 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-87910 | LOW2.91 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28417 | LOW2.81 | xxd 2:9.1.1230-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | fdisk 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.7.1-6+deb13u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-60753 | LOW2.8 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5745 | LOW2.8 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | python3-wheel 0.46.1-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-8354 | LOW2.8 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.3% 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-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73070 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-73074 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-1000382 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32249 | LOW2.8 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89162 | LOW2.8 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 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+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2+deb13u4 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-2013-4392 | LOW2.8 | libsystemd-shared 261.2-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd-shared 261.2-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 261.2-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 261.2-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 261.2-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 261.2-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86141 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW2.78 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-25741 | LOW2.72 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25742 | LOW2.72 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25743 | LOW2.72 | qemu-system-common 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25741 | LOW2.72 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25742 | LOW2.72 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25743 | LOW2.72 | qemu-system-data 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25741 | LOW2.72 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25742 | LOW2.72 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25743 | LOW2.72 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25741 | LOW2.72 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25742 | LOW2.72 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25743 | LOW2.72 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25741 | LOW2.72 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25742 | LOW2.72 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-25743 | LOW2.72 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8367 | LOW2.7 | aria2 1.37.0+debian-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | fdisk 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2023-30571 | LOW2.7 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2-1t64 1.11.1-1+deb13u1 fixed in 1.11.1-1+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15806 | LOW2.7 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW2.7 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15806 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-19672 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58470 | LOW2.7 | wget 1.25.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | xxd 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.64 | xxd 2:9.1.1230-2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1.2+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2008-4677 | LOW2.58 | xxd 2:9.1.1230-2 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-87876 | LOW2.55 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW2.46 | libarchive13t64 3.7.4-4+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | xxd 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW2.38 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-3735 | LOW2.24 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6426 | LOW2.24 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | xxd 2:9.1.1230-2 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-2011-3374 | LOW2.22 | apt-utils 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48102 | LOW2.19 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18739 | LOW2.12 | libpopt0 1.19+dfsg-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.12 | libpopt0 1.19+dfsg-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27139 | LOW2.12 | stdlib v1.25.7 fixed in 1.25.8, 1.26.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | xxd 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | xxd 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW1.99 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1703 | LOW1.99 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-8612 | LOW1.94 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW1.89 | openssl 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18839 | LOW1.87 | libpopt0 1.19+dfsg-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.13-stdlib 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47111 | LOW1.68 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-47112 | LOW1.68 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-29+deb13u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2020-25741 | LOW1.63 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-25742 | LOW1.63 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-25743 | LOW1.63 | qemu-utils 1:11.1.0+ds-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW1.48 | libarchive-tools 3.7.4-4+deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.12 | python3.13 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.12 | python3.13-minimal 3.13.5-2+deb13u4 fixed in 3.13.5-2+deb13u5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | xxd 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2002-1976 | LOW1.07 | net-tools 2.10-1.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6653 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | systemd 261.2-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74860 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% 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-86138 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86139 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86140 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86142 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86144 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11979 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-86143 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.16.1-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2t64 1.2.16.1-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90781 | NONE0 | libasound2-data 1.2.16.1-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90781 | NONE0 | libasound2t64 1.2.16.1-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86137 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-96675 | NONE0 | libasound2-data 1.2.16.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-96675 | NONE0 | libasound2t64 1.2.16.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-76781 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | systemd 261.2-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd 261.2-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd 261.2-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd 261.2-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-96674 | NONE0 | libasound2-data 1.2.16.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-96674 | NONE0 | libasound2t64 1.2.16.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-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-2026-86141 | NONE0 | libxml2-utils 2.12.7+dfsg+really2.9.14-2.1+deb13u3 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-2013-4392 | NONE0 | systemd 261.2-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 261.2-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48095 | NONE0 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58052 | NONE0 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48101 | NONE0 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48104 | NONE0 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48112 | NONE0 | 7zip 25.01+dfsg-1~deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-71832 | NONE0 | aria2 1.37.0+debian-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75421 | NONE0 | aria2 1.37.0+debian-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-80229 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| DSA-6416-2 | NONE0 | jq 1.7.1-6+deb13u3 fixed in 1.7.1-6+deb13u4 | — | Not Applicable |
| CVE-2026-71832 | NONE0 | libaria2-0 1.37.0+debian-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75421 | NONE0 | libaria2-0 1.37.0+debian-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libegl1 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| DSA-6416-2 | NONE0 | libjq1 1.7.1-6+deb13u3 fixed in 1.7.1-6+deb13u4 | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | liblzma5 5.8.1-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-001B0E | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-17A9B4 | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-37DA2F | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-52FEFD | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-575F54 | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-724ECC | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-B9374C | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| TEMP-0000000-D7723D | NONE0 | libntfs-3g89t64 1:2022.10.3-5+deb13u2 No fix yet | — | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| TEMP-1149217-B31E38 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46675 | NONE0 | libpng16-16t64 1.6.58-1 No fix yet | — | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-35189 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-35191 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42772 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54872 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54873 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54875 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-72897 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75804 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75805 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75806 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-77696 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-84782 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-84784 | NONE0 | libssl3t64 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-6727 | NONE0 | libtpms0 0.9.2-3.2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| DSA-6496-2 | NONE0 | nginx 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u9 | — | Not Applicable |
| DSA-6496-2 | NONE0 | nginx-common 1.26.3-3+deb13u7 fixed in 1.26.3-3+deb13u9 | — | Not Applicable |
| CVE-2026-35189 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-35191 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42772 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54872 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54873 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54875 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-72897 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75804 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75805 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75806 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-77696 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-84782 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-84784 | NONE0 | openssl 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-35189 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-35191 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-42772 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54872 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54873 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-54875 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-72897 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75804 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75805 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-75806 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-77696 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-84782 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-84784 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2024-13745 | NONE0 | ovmf-generic 2026.05-2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-16271 | NONE0 | qemu-system-common 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-17588 | NONE0 | qemu-system-common 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66899 | NONE0 | qemu-system-common 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66900 | NONE0 | qemu-system-common 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-77913 | NONE0 | qemu-system-common 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-84788 | NONE0 | qemu-system-common 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-16271 | NONE0 | qemu-system-data 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-17588 | NONE0 | qemu-system-data 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66899 | NONE0 | qemu-system-data 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66900 | NONE0 | qemu-system-data 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-77913 | NONE0 | qemu-system-data 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-84788 | NONE0 | qemu-system-data 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-16271 | NONE0 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-17588 | NONE0 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66899 | NONE0 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66900 | NONE0 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-77913 | NONE0 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-84788 | NONE0 | qemu-system-modules-opengl 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-16271 | NONE0 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-17588 | NONE0 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66899 | NONE0 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66900 | NONE0 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-77913 | NONE0 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-84788 | NONE0 | qemu-system-modules-spice 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-16271 | NONE0 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-17588 | NONE0 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66899 | NONE0 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66900 | NONE0 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-77913 | NONE0 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-84788 | NONE0 | qemu-system-x86 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-16271 | NONE0 | qemu-utils 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-17588 | NONE0 | qemu-utils 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66899 | NONE0 | qemu-utils 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-66900 | NONE0 | qemu-utils 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-77913 | NONE0 | qemu-utils 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| CVE-2026-84788 | NONE0 | qemu-utils 1:11.1.0+ds-2 No fix yet | — | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | xz-utils 5.8.1-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.