This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve remote code execution (CVE-2023-45853), cause denial of service (CVE-2018-20796), or gain sensitive information by exploiting critical vulnerabilities like CVE-2019-8457 in core libraries like glibc, zlib, and SQLite. While this is an Official Docker Hub Image, the presence of 8 high-severity vulnerabilities (7.0 or higher) and a maximum severity of 10.0 warrants an immediate halt to deployment. Note that CVE-2023-45853 requires the container's application to utilize the MiniZip component of zlib for processing untrusted zip files, and some glibc vulnerabilities such as CVE-2026-0861 are less exploitable due to specific input control requirements.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-8457 | CRITICAL10 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 30.7% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2023-45853 | HIGH7.84 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.31-13+deb11u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2018-20796 | HIGH7.5 | libc6 2.31-13+deb11u13 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-9538 | HIGH7.5 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Directly ExposedContext importance: HIGH |
| CVE-2019-1010023 | HIGH7.48 | libc-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | HIGH7.1 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | — | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42010 | MEDIUM6.66 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2017-7245 | MEDIUM6.63 | libpcre3 2:8.39-13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-7246 | MEDIUM6.63 | libpcre3 2:8.39-13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.56 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5260 | MEDIUM6.56 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2019-9192 | MEDIUM6.38 | libc-bin 2.31-13+deb11u13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6 2.31-13+deb11u13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-33560 | MEDIUM6.38 | libgcrypt20 1.8.7-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-6829 | MEDIUM6.38 | libgcrypt20 1.8.7-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-11164 | MEDIUM6.38 | libpcre3 2:8.39-13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20838 | MEDIUM6.38 | libpcre3 2:8.39-13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-4899 | MEDIUM6.38 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM6.18 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42009 | MEDIUM6 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u13 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u13 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM5.3 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | — | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM5.18 | libsystemd0 247.3-7+deb11u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM5.18 | libudev1 247.3-7+deb11u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.02 | libc6 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.02 | libgcrypt20 1.8.7-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.02 | libtasn1-6 4.16.0-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-4 No fix yet | — | Directly Exposed |
| CVE-2005-2541 | MEDIUM4.8 | tar 1.34+dfsg-1+deb11u1 No fix yet | 3.8% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.11.dfsg-2+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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.31-13+deb11u13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.31-13+deb11u13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2.1~deb11u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | MEDIUM4.37 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Post-ExploitContext importance: MEDIUM |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30 3.7.1-5+deb11u9 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | MEDIUM4.13 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | MEDIUM4.08 | gcc-10-base 10.2.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | gcc-9-base 9.3.0-22 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 10.2.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 10.2.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| 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-2024-10041 | MEDIUM4 | libpam-modules 1.4.0-9+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam0g 1.4.0-9+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.2.4 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42497 | LOW3.6 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Post-ExploitContext importance: MEDIUM |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | LOW3.53 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.31-13+deb11u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.31-13+deb11u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.7-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-bin 2.31-13+deb11u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6 2.31-13+deb11u13 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1+deb11u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.7 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1: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.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.3% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.27-2+deb11u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.27-2+deb11u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | login 1:4.8.1-1+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.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.2.4 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | login 1:4.8.1-1+deb11u1 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.8.1-1+deb11u1 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.27-2+deb11u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.1-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42014 | NONE0 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | — | 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-48959 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | — | 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 |