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. It is an official, digest-pinned Node image, but it still ships 305 exposed-surface issues, 65 of them rated 7.0 or higher with a maximum of 9.1. An attacker able to feed malformed Kerberos or ASN.1/TLS input into a service built on top could trigger memory corruption or denial of service, and on 32-bit platforms the PAC-parsing integer overflow in CVE-2022-42898 can escalate to remote code execution. CVE-2024-37371 (9.1) is the top-rated inherited finding and needs only a malformed GSS token to hit. Rebuilding from the current node image tag, which carries patched krb5 and OpenSSL packages, fully eliminates these inherited findings. The 120 post-exploit-only items (max 4.68) matter only after a host is already compromised, so they do not change the verdict. 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-2024-37371 | CRITICAL9.1 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.31-13+deb11u4 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.31-13+deb11u4 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssapi-krb5-2 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 75.1% Actively Exploited | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-78408 | HIGH7.9 | libblkid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78408 | HIGH7.9 | libmount1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78408 | HIGH7.9 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78408 | HIGH7.9 | libuuid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-76642 | HIGH7.8 | libblkid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78410 | HIGH7.8 | libblkid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libcom-err2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libext2fs2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-76642 | HIGH7.8 | libmount1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78410 | HIGH7.8 | libmount1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre3 2:8.39-13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-76642 | HIGH7.8 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78410 | HIGH7.8 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2022-1304 | HIGH7.8 | libss2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-76642 | HIGH7.8 | libuuid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78410 | HIGH7.8 | libuuid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.31-13+deb11u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.31-13+deb11u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.31-13+deb11u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.31-13+deb11u4 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-2018-6829 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.18.3-6+deb11u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.18.3-6+deb11u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.18.3-6+deb11u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.18.3-6+deb11u2 No fix yet | 2.1% 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-2017-11164 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 3.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-2023-0215 | HIGH7.5 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | HIGH7.5 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 1.3% 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-2022-25881 | HIGH7.5 | http-cache-semantics 4.1.0 fixed in 4.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25883 | HIGH7.5 | semver 7.3.7 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 247.3-7+deb11u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 247.3-7+deb11u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libblkid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libblkid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libmount1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libmount1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libuuid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libuuid1 2.36.1-8+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u2 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+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM6.38 | brace-expansion 2.0.1 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM6.38 | diff 5.1.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 3.1.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | minimatch 5.1.0 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 247.3-7+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 247.3-7+deb11u1 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-42012 | MEDIUM6.03 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.18.3-6+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u4 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5+deb11u2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | minimatch 5.1.0 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 247.3-7+deb11u1 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-2024-33600 | MEDIUM5.3 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.31-13+deb11u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u4 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u4 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1v-0~deb11u1 | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1v-0~deb11u1 | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1-6 4.16.0-2 fixed in 4.16.0-2+deb11u2 | 1.1% 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-2026-18938 | 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+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.31-13+deb11u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.31-13+deb11u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u2 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+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | minimatch 5.1.0 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.31-13+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.31-13+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.36.1-8+deb11u1 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+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 247.3-7+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3821 | MEDIUM4.67 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4415 | MEDIUM4.67 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 247.3-7+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.36.1-8+deb11u1 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-13221 | MEDIUM4.64 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u2 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+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libblkid1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libmount1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libsmartcols1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28085 | MEDIUM4.4 | libuuid1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.31-13+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2026-24842 | MEDIUM4.18 | tar 6.1.11 fixed in 7.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.31-13+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.31-13+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2961 | MEDIUM4.12 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Post-Exploit |
| 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+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.31-13+deb11u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 1.1% 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-2020-16156 | LOW3.98 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW3.82 | tar 6.1.11 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW3.82 | tar 6.1.11 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW3.82 | tar 6.1.11 fixed in 7.5.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW3.82 | tar 6.1.11 fixed in 7.5.18 | 0.6% 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-2024-9143 | LOW3.7 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u2 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4911 | LOW3.65 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u7 | 81.4% Actively Exploited | Post-Exploit |
| CVE-2023-4911 | LOW3.65 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u7 | 81.4% Actively Exploited | Post-Exploit |
| CVE-2026-26960 | LOW3.62 | tar 6.1.11 fixed in 7.5.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.31-13+deb11u4 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.31-13+deb11u4 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls30 3.7.1-5+deb11u2 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-2024-29415 | LOW3.53 | ip 2.0.0 No fix yet | 8.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-42282 | LOW3.53 | ip 2.0.0 fixed in 2.0.1, 1.1.9 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50387 | LOW3.51 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u6 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-50868 | LOW3.51 | libsystemd0 247.3-7+deb11u1 fixed in 247.3-7+deb11u6 | 81.7% Actively Exploited | Post-Exploit |
| CVE-2023-50387 | LOW3.51 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u6 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-50868 | LOW3.51 | libudev1 247.3-7+deb11u1 fixed in 247.3-7+deb11u6 | 81.7% Actively Exploited | Post-Exploit |
| CVE-2023-0286 | LOW3.46 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1n-0+deb11u4 | 59.5% Actively Exploited | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.31-13+deb11u4 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.1-5+deb11u2 fixed in 3.7.1-5+deb11u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl1.1 1.1.1n-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3449 | LOW3.4 | @tootallnate/once 2.0.0 fixed in 3.0.1, 2.0.1 | 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-2025-15649 | LOW3.31 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28863 | LOW3.31 | tar 6.1.11 fixed in 6.2.1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-48303 | LOW3.3 | tar 1.34+dfsg-1 fixed in 1.34+dfsg-1+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37371 | LOW3.28 | libgssapi-krb5-2 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37371 | LOW3.28 | libk5crypto3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37371 | LOW3.28 | libkrb5-3 1.18.3-6+deb11u2 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-46848 | LOW3.28 | libtasn1-6 4.16.0-2 fixed in 4.16.0-2+deb11u1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-29786 | LOW3.21 | tar 6.1.11 fixed in 7.5.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.36.1-8+deb11u1 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-2026-56392 | 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+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-23745 | LOW3.11 | tar 6.1.11 fixed in 7.5.3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-23950 | LOW3.01 | tar 6.1.11 fixed in 7.5.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-31484 | LOW2.92 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u4 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.32.1-4+deb11u2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.36.1-8+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u1 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 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31802 | LOW2.8 | tar 6.1.11 fixed in 7.5.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW2.8 | tar 6.1.11 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-36084 | LOW2.8 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36085 | LOW2.8 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-36086 | LOW2.8 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-36087 | LOW2.8 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 247.3-7+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 247.3-7+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u1 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+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW2.7 | tar 6.1.11 fixed in 7.5.17 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5889 | LOW2.63 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5889 | LOW2.63 | brace-expansion 2.0.1 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | LOW2.55 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% 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+deb11u1 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-2025-30258 | LOW2.4 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.36.1-8+deb11u1 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+deb11u1 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 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1 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-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 | 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+deb11u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.34+dfsg-1 fixed in 1.34+dfsg-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-1304 | NONE0 | e2fsprogs 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Not Applicable |
| 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-2023-29491 | NONE0 | libtinfo6 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1304 | NONE0 | logsave 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-bin 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-29458 | NONE0 | libtinfo6 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-base 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-bin 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.7-1 No fix yet | 0.1% 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-4641 | NONE0 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login 1:4.8.1-1 No fix yet | 0.9% 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-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-2013-4235 | NONE0 | login 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.2+20201114-2 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+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.12 fixed in 1.20.14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.36.1-8+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.36.1-8+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21C4F8 | NONE0 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8188AC | NONE0 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0000000-A5518C | NONE0 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0000000-B05303 | NONE0 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | libssl1.1 1.1.1n-0+deb11u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.36.1-8+deb11u1 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+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% 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 No fix yet | — | Not Applicable |
| DLA-3972-1 | NONE0 | tzdata 2021a-1+deb11u6 fixed in 2024b-0+deb11u1 | — | Not Applicable |
| DLA-4085-1 | NONE0 | tzdata 2021a-1+deb11u6 fixed in 2025a-0+deb11u1 | — | Not Applicable |
| DLA-4105-1 | NONE0 | tzdata 2021a-1+deb11u6 fixed in 2025b-0+deb11u1 | — | Not Applicable |
| DLA-4403-1 | NONE0 | tzdata 2021a-1+deb11u6 fixed in 2025b-0+deb11u2 | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2021a-1+deb11u6 fixed in 2026b-0+deb11u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.36.1-8+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-9496 | NONE0 | pacote 13.6.2 fixed in 21.5.1 | 0.3% 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.