Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. The main practical risks are inherited components that can cause denial of service in downstream services using OpenSSL CMP (CVE-2026-63076) or local privilege escalation where systemd-homed is active (CVE-2026-16742). CVE-2026-63076 only applies when CMP PBM verification is enabled, and CVE-2026-16742 requires systemd-homed; disabling or not using those features fully removes those specific risks. Post-exploit-only findings exist but are lower severity (0 at 6.0+; max 4.06) and do not change the CAUTION verdict. Rebuild on a patched base or update the inherited packages before shipping production images. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-41409 | HIGH7.5 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | HIGH7.5 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 247.3-7+deb11u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 247.3-7+deb11u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM6.97 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM6.8 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM6.63 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | MEDIUM6.46 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | MEDIUM6.29 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM6.29 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.2.53-10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-bin 2.31-13+deb11u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-bin 2.31-13+deb11u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6 2.31-13+deb11u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6 2.31-13+deb11u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM5.95 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u14 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u14 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u14 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u14 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2+deb11u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | MEDIUM5.52 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | MEDIUM5.52 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM5.52 | libtirpc-common 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM5.52 | libtirpc3 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.2.53-10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.4.48-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.23.22-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.23.22-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-bin 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-bin 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6 2.31-13+deb11u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | MEDIUM5.02 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM5.02 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.8 | libgcc-s1 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.8 | libstdc++6 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.31-13+deb11u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.31-13+deb11u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84784 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM4.5 | libtirpc-common 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM4.5 | libtirpc3 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u14 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.31-13+deb11u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.31-13+deb11u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-8457 | MEDIUM4.06 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.31-13+deb11u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1+deb11u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW3.57 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW3.57 | libc-bin 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.31-13+deb11u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.31-13+deb11u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.31-13+deb11u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.31-13+deb11u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97399 | LOW3.15 | libc-bin 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6 2.31-13+deb11u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.15 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.15 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.15 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.32.1-4+deb11u5 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2017-7245 | LOW2.81 | libpcre3 2:8.39-13 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7246 | LOW2.81 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.8 | dash 0.5.11+git20200708+dd9ef66-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89162 | LOW2.8 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW2.78 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.31-13+deb11u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc-bin 2.31-13+deb11u14 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.31-13+deb11u14 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc6 2.31-13+deb11u14 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33560 | LOW2.7 | libgcrypt20 1.8.7-6 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6829 | LOW2.7 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libgssapi-krb5-2 1.18.3-6+deb11u8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libk5crypto3 1.18.3-6+deb11u8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5-3 1.18.3-6+deb11u8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5support0 1.18.3-6+deb11u8 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-11164 | LOW2.7 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-20838 | LOW2.7 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.7-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW2.57 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.45 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.42 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.34+dfsg-1+deb11u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.11+git20200708+dd9ef66-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-10-base 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-9-base 9.3.0-22 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-9+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-9+deb11u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4235 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.1-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30 3.7.1-5+deb11u10 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-1147318-639065 | NONE0 | liblzma5 5.2.5-2.1~deb11u2 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1w-0+deb11u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 2.96-7+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.4% 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.