Last scanned:
This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The scan found 327 exposed findings, and only one, CVE-2019-8457 in libdb5.3, is rated at 6.0 or higher and could affect the verdict. That flaw is a read-side memory issue that matters only if an application opens crafted SQLite R-tree data, which the default setup does not do, so it is unlikely to cause harm in this container. The container runs as root by default, so reducing privileges is a sensible hardening step even though it is not tied to a specific finding.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-8457 | MEDIUM6 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 45.4% High Exploitation Risk | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.88 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | MEDIUM5.88 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.31-13+deb11u11 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.31-13+deb11u11 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM5.46 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.31-13+deb11u11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.31-13+deb11u11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 247.3-7+deb11u6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 247.3-7+deb11u6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.31-13+deb11u11 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.31-13+deb11u11 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32988 | MEDIUM4.92 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.92 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.92 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.31-13+deb11u11 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.31-13+deb11u11 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM4.86 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM4.86 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM4.86 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4.7 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4.7 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4598 | MEDIUM4.7 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-33560 | MEDIUM4.5 | libgcrypt20 1.8.7-6 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libgssapi-krb5-2 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libgssapi-krb5-2 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libk5crypto3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libk5crypto3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5-3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5-3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5support0 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5support0 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-4899 | MEDIUM4.5 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM4.44 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM4.44 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.44 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.2.53-10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM4.26 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.31-13+deb11u11 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.31-13+deb11u11 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.31-13+deb11u11 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.31-13+deb11u11 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM4.18 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.31-13+deb11u11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.31-13+deb11u11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42014 | LOW3.96 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libgssapi-krb5-2 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.18.3-6+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libk5crypto3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.18.3-6+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libkrb5-3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.18.3-6+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libkrb5support0 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.18.3-6+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc-common 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc3 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | gcc-10-base 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | gcc-9-base 9.3.0-22 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.31-13+deb11u11 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.31-13+deb11u11 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | libgcc-s1 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | libstdc++6 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | LOW3.9 | libsystemd0 247.3-7+deb11u6 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | LOW3.9 | libudev1 247.3-7+deb11u6 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.2.53-10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.4.48-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.23.22-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | LOW3.72 | libp11-kit0 0.23.22-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.31-13+deb11u11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.31-13+deb11u11 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | LOW3.54 | libtasn1-6 4.16.0-2+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8376 | LOW3.53 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW3.42 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | LOW3.31 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | LOW3.31 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW3.3 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW3.28 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW3.18 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-12243 | LOW3.18 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14831 | LOW3.18 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | LOW3.18 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | LOW3.18 | liblzma5 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-12133 | LOW3.18 | libtasn1-6 4.16.0-2+deb11u1 fixed in 4.16.0-2+deb11u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc-common 1.3.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc3 1.3.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | LOW3.18 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | LOW3.04 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-57432 | LOW3.02 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-3576 | LOW3.01 | libgssapi-krb5-2 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libk5crypto3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libkrb5-3 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libkrb5support0 1.18.3-6+deb11u5 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | LOW3.01 | perl-base 5.32.1-4+deb11u4 fixed in 5.32.1-4+deb11u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | LOW3 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | LOW3 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.18.3-6+deb11u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.18.3-6+deb11u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.18.3-6+deb11u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.18.3-6+deb11u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41991 | LOW2.82 | gzip 1.10-4+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | LOW2.81 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.81 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW2.81 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41992 | LOW2.7 | gzip 1.10-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1+deb11u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpgv 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9820 | LOW2.4 | libgnutls30 3.7.1-5+deb11u6 fixed in 3.7.1-5+deb11u9 | 0.2% Theoretical Threat | Directly Exposed |
| TEMP-1147318-639065 | LOW2.4 | liblzma5 5.2.5-2.1~deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 8.32-4+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.34 | dash 0.5.11+git20200708+dd9ef66-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.11+git20200708+dd9ef66-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.7-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | LOW2.34 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW2.34 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW2.34 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW2.34 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW2.34 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW2.34 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.18.3-6+deb11u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.18.3-6+deb11u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.18.3-6+deb11u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.18.3-6+deb11u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.18.3-6+deb11u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.18.3-6+deb11u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.18.3-6+deb11u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.18.3-6+deb11u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.18.3-6+deb11u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.18.3-6+deb11u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.18.3-6+deb11u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.18.3-6+deb11u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.34 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-base 5.32.1-4+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1+deb11u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | apt 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW1.99 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.18.3-6+deb11u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.18.3-6+deb11u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.18.3-6+deb11u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.18.3-6+deb11u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW1.99 | login 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW1.99 | passwd 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89162 | LOW1.98 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29383 | LOW1.68 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.1-2+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-95209 | LOW1.5 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95210 | LOW1.5 | libgnutls30 3.7.1-5+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.8.1-1 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.8.1-1 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 2.96-7+deb11u1 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2025-6297 | LOW1.27 | dpkg 1.20.13 fixed in 1.20.14 | 0.5% Theoretical Threat | Post-Exploit |
| DLA-4085-1 | NONE0 | tzdata 2024b-0+deb11u1 fixed in 2025a-0+deb11u1 | — | Not Applicable |
| DLA-4105-1 | NONE0 | tzdata 2024b-0+deb11u1 fixed in 2025b-0+deb11u1 | — | Not Applicable |
| DLA-4403-1 | NONE0 | tzdata 2024b-0+deb11u1 fixed in 2025b-0+deb11u2 | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2024b-0+deb11u1 fixed in 2026b-0+deb11u1 | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.