Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit remotely reachable denial-of-service flaws in GnuTLS (CVE-2026-33846) and OpenSSL (CVE-2026-28388) to crash the service or cause memory corruption, while the libgcrypt side-channel could expose sensitive data. Post-exploit-only findings are low severity (max 4.06), so the main concern is the exposed network surface. Some OpenSSL issues require delta CRL processing to be enabled, so disabling that feature reduces exposure. Despite the trustworthy provenance (pinned digest, 37M+ pulls), the vulnerability set warrants caution for production.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.31-13+deb11u11 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.31-13+deb11u11 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33560 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-41409 | HIGH7.5 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 1.0% 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-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 247.3-7+deb11u6 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 247.3-7+deb11u6 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.2.53-10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u13 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u13 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u11 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u11 No fix yet | 1.7% 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+deb11u6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u6 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.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5+deb11u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | <0.1% 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+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u11 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u11 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.23.22-1 No fix yet | 0.1% 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+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u11 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u6 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 0.6% 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-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u12 | 0.3% 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-22795 | MEDIUM4.67 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 0.6% 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.1% 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-0915 | MEDIUM4.5 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.31-13+deb11u11 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% 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.1% 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-42766 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u11 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u11 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u11 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 10.2.1-6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 10.2.1-6 No fix yet | 0.8% 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-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-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-68160 | MEDIUM4 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u7 | 0.7% 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+deb11u11 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u11 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-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% 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-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-2019-1010022 | LOW3.53 | libc-bin 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.31-13+deb11u11 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.31-13+deb11u11 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.31-13+deb11u11 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| 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.1% 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-2025-40909 | LOW3.01 | perl-base 5.32.1-4+deb11u4 fixed in 5.32.1-4+deb11u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-32988 | LOW2.95 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl1.1 1.1.1w-0+deb11u2 fixed in 1.1.1w-0+deb11u8 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.32.1-4+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-7245 | LOW2.81 | libpcre3 2:8.39-13 No fix yet | 2.3% 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-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-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% 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-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-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.2% 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-40228 | LOW2.8 | libudev1 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | LOW2.78 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.31-13+deb11u11 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.31-13+deb11u11 No fix yet | 5.8% 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+deb11u6 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libk5crypto3 1.18.3-6+deb11u6 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5-3 1.18.3-6+deb11u6 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5support0 1.18.3-6+deb11u6 No fix yet | 2.1% 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-2026-13595 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% 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-13595 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% 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+deb11u4 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.1% 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+deb11u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1 No fix yet | 0.9% 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-2013-4235 | LOW2.4 | login 1:4.8.1-1 No fix yet | 0.3% 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 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-2026-41992 | LOW2.29 | gzip 1.10-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW2.29 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.29 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 8.32-4+b1 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-2025-15649 | LOW1.99 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| 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-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-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 | Post-Exploit |
| CVE-2025-6020 | NONE0 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68973 | NONE0 | gpgv 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-10-base 10.2.1-6 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-9-base 9.3.0-22 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.27-2+deb11u2 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-53615 | NONE0 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.7-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.13 fixed in 1.20.14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1w-0+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.8.1-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% 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 |
| 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 |
| CVE-2026-53615 | NONE0 | util-linux 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
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.