Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker reaching the exposed HTTP/2 port could exhaust the gateway with request floods via CVE-2023-44487 or crash it with malformed frames, and CVE-2026-111497 could, if Brotli decoding is reachable, lead to memory corruption and code execution. CVE-2024-2961 only matters if the gateway performs the specific iconv conversion, which it does not normally do, so it should be checked against the deployment's actual configuration. The post-compromise findings are low severity and do not change this verdict, but the exposed HTTP/2 and decoder flaws make this image unsuitable for internet-facing production use until they are addressed through patching or strict upstream controls.
Hardening plan for this image · 5 steps. The first targets 2 actively exploited CVEs.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.43.0-1 fixed in 1.43.0-1+deb11u1 | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2024-2961 | HIGH8 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2024-2961 | HIGH8 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111497 | HIGH8 | libbrotli1 1.0.9-2+b2 No fix yet | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-27135 | HIGH7.5 | libnghttp2-14 1.43.0-1 fixed in 1.43.0-1+deb11u3 | 0.8% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-54371 | MEDIUM6.3 | libattr1 1:2.4.48-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM6.2 | libp11-kit0 0.23.22-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM6.2 | libp11-kit0 0.23.22-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u6 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u6 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | MEDIUM5.88 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | MEDIUM5.88 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1n-0+deb11u4 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+deb11u4 fixed in 1.1.1w-0+deb11u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28182 | MEDIUM5.51 | libnghttp2-14 1.43.0-1 fixed in 1.43.0-1+deb11u2 | 85.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.31-13+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.31-13+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 247.3-7+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 247.3-7+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | MEDIUM5.46 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | MEDIUM5.46 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | MEDIUM5.46 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | MEDIUM5.46 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | MEDIUM5.46 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13221 | MEDIUM5.46 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | MEDIUM5.46 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM5.4 | libnghttp2-14 1.43.0-1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.31-13+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.31-13+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM5.3 | liblzma5 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 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+deb11u4 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+deb11u4 fixed in 1.1.1w-0+deb11u2 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl1.1 1.1.1n-0+deb11u4 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+deb11u1 fixed in 4.16.0-2+deb11u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27533 | MEDIUM5.28 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27534 | MEDIUM5.28 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27533 | MEDIUM5.28 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27534 | MEDIUM5.28 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43551 | MEDIUM5.17 | curl 7.74.0-1.3+deb11u7 No fix yet | 16.6% High Exploitation Risk | Directly Exposed |
| CVE-2024-2398 | MEDIUM5.17 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u12 | 36.1% High Exploitation Risk | Directly Exposed |
| CVE-2022-43551 | MEDIUM5.17 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 16.6% High Exploitation Risk | Directly Exposed |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u12 | 36.1% High Exploitation Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM5.04 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-7008 | MEDIUM5.02 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.31-13+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.31-13+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32988 | MEDIUM4.92 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42013 | MEDIUM4.92 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM4.92 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.31-13+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.31-13+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.86 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.86 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-92392 | MEDIUM4.86 | curl 7.74.0-1.3+deb11u7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.86 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | MEDIUM4.86 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-92392 | MEDIUM4.86 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u4 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2026-54875 | MEDIUM4.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4.7 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-4598 | MEDIUM4.7 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u12 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-23914 | MEDIUM4.64 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-23914 | MEDIUM4.64 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-38545 | MEDIUM4.58 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u10 | 78.7% Actively Exploited | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u10 | 78.7% Actively Exploited | Post-Exploit |
| CVE-2022-42916 | MEDIUM4.5 | curl 7.74.0-1.3+deb11u7 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.5 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-42916 | MEDIUM4.5 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5773 | MEDIUM4.5 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-0553 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM4.5 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM4.5 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-22218 | MEDIUM4.5 | libssh2-1 1.9.0-2 fixed in 1.9.0-2+deb11u1 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58050 | MEDIUM4.5 | libssh2-1 1.9.0-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-0464 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u13 | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2024-7264 | MEDIUM4.48 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u13 | 20.2% High Exploitation Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM4.44 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM4.44 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM4.26 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58471 | MEDIUM4.26 | wget 1.21-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58472 | MEDIUM4.26 | wget 1.21-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.31-13+deb11u6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.31-13+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.31-13+deb11u6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.31-13+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.31-13+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM4.18 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u8 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.31-13+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.31-13+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% 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-4105 | MEDIUM4.02 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| TEMP-1147318-639065 | MEDIUM4 | liblzma5 5.2.5-2.1~deb11u1 No fix yet | — | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6020 | LOW3.98 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-16156 | LOW3.98 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-47038 | LOW3.98 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | LOW3.96 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-46218 | LOW3.9 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u11 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u11 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9681 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3784 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | LOW3.9 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.18.3-6+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | LOW3.9 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.18.3-6+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | LOW3.9 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.18.3-6+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-36054 | LOW3.9 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u4 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-24528 | LOW3.9 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.18.3-6+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15661 | LOW3.9 | libssh2-1 1.9.0-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58051 | LOW3.9 | libssh2-1 1.9.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66032 | LOW3.9 | libssh2-1 1.9.0-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc-common 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc3 1.3.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-10524 | LOW3.9 | wget 1.21-1+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58469 | LOW3.9 | wget 1.21-1+deb11u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | gcc-10-base 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | gcc-9-base 9.3.0-22 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.31-13+deb11u6 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.31-13+deb11u6 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | libgcc-s1 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | LOW3.9 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4039 | LOW3.9 | libstdc++6 10.2.1-6 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | LOW3.9 | libsystemd0 247.3-7+deb11u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | LOW3.9 | libudev1 247.3-7+deb11u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | LOW3.83 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | LOW3.83 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | LOW3.83 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | LOW3.83 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.7-1 No fix yet | 0.1% 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-2026-97399 | LOW3.7 | libc-bin 2.31-13+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.31-13+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.21-1+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4911 | LOW3.65 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u7 | 63.8% Actively Exploited | Post-Exploit |
| CVE-2023-4911 | LOW3.65 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u7 | 63.8% Actively Exploited | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | libsqlite3-0 3.34.1-3 No fix yet | 73.5% Actively Exploited | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-27535 | LOW3.54 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27536 | LOW3.54 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-28321 | LOW3.54 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-27535 | LOW3.54 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27536 | LOW3.54 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-28321 | LOW3.54 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u9 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-5981 | LOW3.54 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-66034 | LOW3.54 | libssh2-1 1.9.0-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | LOW3.54 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-72897 | LOW3.54 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-75805 | LOW3.54 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-77696 | LOW3.54 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-5535 | LOW3.54 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69420 | LOW3.54 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.54 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.54 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.54 | wget 1.21-1+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | LOW3.53 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-50387 | LOW3.51 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u6 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-50868 | LOW3.51 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u6 | 74.3% Actively Exploited | Post-Exploit |
| CVE-2023-50387 | LOW3.51 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u6 | 100.0% Actively Exploited | Post-Exploit |
| CVE-2023-50868 | LOW3.51 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u6 | 74.3% Actively Exploited | Post-Exploit |
| CVE-2026-3783 | LOW3.42 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | LOW3.42 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | LOW3.36 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u4 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW3.36 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-8096 | LOW3.31 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u14 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-23915 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-8096 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u14 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | LOW3.31 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u8 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | LOW3.31 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 247.3-7+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 247.3-7+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 247.3-7+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 247.3-7+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 247.3-7+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 247.3-7+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-27538 | LOW3.3 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27538 | LOW3.3 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u8 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | LOW3.3 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22795 | LOW3.3 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW3.3 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW3.3 | libsystemd0 247.3-7+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 247.3-7+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | LOW3.28 | libssh2-1 1.9.0-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-46219 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-12243 | LOW3.18 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14831 | LOW3.18 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u9 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | LOW3.18 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc-common 1.3.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc3 1.3.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-0465 | LOW3.18 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0466 | LOW3.18 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW3.18 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1v-0~deb11u1 | 6.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW3.18 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1v-0~deb11u1 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW3.18 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42772 | LOW3.18 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54873 | LOW3.18 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-75804 | LOW3.18 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-75806 | LOW3.18 | openssl 1.1.1n-0+deb11u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-84784 | LOW3.18 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12087 | LOW3.18 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58470 | LOW3.18 | wget 1.21-1+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | LOW3.17 | libsystemd0 247.3-7+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libudev1 247.3-7+deb11u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 75.4% Actively Exploited | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1n-0+deb11u5 | 75.4% Actively Exploited | Post-Exploit |
| CVE-2011-3389 | LOW3.04 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libgssapi-krb5-2 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libk5crypto3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libkrb5-3 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | LOW3.01 | libkrb5support0 1.18.3-6+deb11u3 fixed in 1.18.3-6+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | LOW3.01 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW3 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48959 | LOW3 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | LOW3 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | LOW2.95 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.18.3-6+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.18.3-6+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.18.3-6+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.18.3-6+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | LOW2.92 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | LOW2.92 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u8 | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW2.89 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 52.4% Actively Exploited | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41991 | LOW2.82 | gzip 1.10-4+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | LOW2.82 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.82 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-1304 | LOW2.81 | e2fsprogs 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-1304 | LOW2.81 | libcom-err2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1304 | LOW2.81 | libext2fs2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.2+20201114-2+deb11u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.81 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11822 | LOW2.81 | libsqlite3-0 3.34.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11824 | LOW2.81 | libsqlite3-0 3.34.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-1304 | LOW2.81 | libss2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-29111 | LOW2.81 | libsystemd0 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.2+20201114-2+deb11u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.81 | libudev1 247.3-7+deb11u2 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-1304 | LOW2.81 | logsave 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.2+20201114-2+deb11u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.2+20201114-2+deb11u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-22365 | LOW2.8 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-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+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-38428 | LOW2.78 | wget 1.21-1+deb11u1 fixed in 1.21-1+deb11u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-33599 | LOW2.74 | libc-bin 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-33599 | LOW2.74 | libc6 2.31-13+deb11u6 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-103111 | LOW2.74 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.10-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-33560 | LOW2.7 | libgcrypt20 1.8.7-6 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-2953 | LOW2.7 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-2953 | LOW2.7 | libldap2-dev 2.4.57+dfsg-3+deb11u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107161 | LOW2.7 | libsasl2-2 2.1.27+dfsg-2.1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107161 | LOW2.7 | libsasl2-modules-db 2.1.27+dfsg-2.1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-36690 | LOW2.7 | libsqlite3-0 3.34.1-3 fixed in 3.34.1-3+deb11u1 | 3.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69421 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54874 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.7 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-4899 | LOW2.7 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69421 | LOW2.7 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW2.7 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW2.7 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-63076 | LOW2.7 | openssl 1.1.1n-0+deb11u4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54874 | LOW2.7 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW2.7 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-28834 | LOW2.7 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-89157 | LOW2.66 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW2.66 | libssl1.1 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-84782 | LOW2.66 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW2.66 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-7104 | LOW2.63 | libsqlite3-0 3.34.1-3 fixed in 3.34.1-3+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92386 | LOW2.58 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | LOW2.56 | libacl1 2.2.53-10 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-28835 | LOW2.55 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | LOW2.52 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | dirmngr 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gnupg-utils 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg-agent 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg-wks-client 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpg-wks-server 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpgconf 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpgsm 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW2.52 | gpgv 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-13176 | LOW2.4 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Post-Exploit |
| DLA-4213-1 | LOW2.4 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u15 | — | Directly Exposed |
| DLA-4432-1 | LOW2.4 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u16 | — | Directly Exposed |
| DLA-4213-1 | LOW2.4 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u15 | — | Directly Exposed |
| DLA-4432-1 | LOW2.4 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u16 | — | Directly Exposed |
| CVE-2025-9820 | LOW2.4 | libgnutls30 3.7.1-5+deb11u3 fixed in 3.7.1-5+deb11u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.4 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW2.4 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-29491 | LOW2.39 | libncursesw6 6.2+20201114-2+deb11u1 fixed in 6.2+20201114-2+deb11u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-29491 | LOW2.39 | libtinfo6 6.2+20201114-2+deb11u1 fixed in 6.2+20201114-2+deb11u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-29491 | LOW2.39 | ncurses-base 6.2+20201114-2+deb11u1 fixed in 6.2+20201114-2+deb11u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-29491 | LOW2.39 | ncurses-bin 6.2+20201114-2+deb11u1 fixed in 6.2+20201114-2+deb11u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libncursesw6 6.2+20201114-2+deb11u1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-89158 | LOW2.34 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW2.34 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libtinfo6 6.2+20201114-2+deb11u1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.2+20201114-2+deb11u1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-bin 6.2+20201114-2+deb11u1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56391 | LOW2.34 | coreutils 8.32-4+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-22922 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-22923 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-28320 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2379 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10966 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.34 | dash 0.5.11+git20200708+dd9ef66-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.11+git20200708+dd9ef66-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.7-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-22922 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-22923 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-28320 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2379 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10966 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW2.34 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW2.34 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW2.34 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW2.34 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.18.3-6+deb11u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.18.3-6+deb11u3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.18.3-6+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.18.3-6+deb11u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.18.3-6+deb11u3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.18.3-6+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.18.3-6+deb11u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.18.3-6+deb11u3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.18.3-6+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.18.3-6+deb11u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.18.3-6+deb11u3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.18.3-6+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-base 5.32.1-4+deb11u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48303 | LOW2.34 | tar 1.34+dfsg-1 fixed in 1.34+dfsg-1+deb11u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-16599 | LOW2.34 | wget 1.21-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW2.27 | libacl1 2.2.53-10 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-2023-28322 | LOW2.22 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38546 | LOW2.22 | curl 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u10 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-28322 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u9 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38546 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 fixed in 7.74.0-1.3+deb11u10 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW2.22 | openssl 1.1.1n-0+deb11u4 fixed in 1.1.1w-0+deb11u2 | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-35189 | LOW2.22 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-35191 | LOW2.22 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-75803 | LOW2.22 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW2.12 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-27587 | LOW2.12 | libssl1.1 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW1.99 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.18.3-6+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.18.3-6+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.18.3-6+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.18.3-6+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW1.99 | login 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW1.99 | passwd 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50812 | LOW1.98 | libsqlite3-0 3.34.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50813 | LOW1.98 | libsqlite3-0 3.34.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW1.91 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | mount 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | mount 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.86 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | curl 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | libcurl4 7.74.0-1.3+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-29383 | LOW1.68 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-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 | Directly Exposed |
| 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-35737 | LOW1.61 | libsqlite3-0 3.34.1-3 No fix yet | 23.6% High Exploitation Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | bsdutils 1:2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | libblkid1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | libmount1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | libsmartcols1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | libuuid1 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | mount 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW1.58 | util-linux 2.36.1-8+deb11u1 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.1-2+deb11u1 No fix yet | — | Post-Exploit |
| CVE-2026-95209 | LOW1.5 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95210 | LOW1.5 | libgnutls30 3.7.1-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.8.1-1 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.8.1-1 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 2.96-7+deb11u1 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1 No fix yet | — | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-6829 | LOW1.4 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2236 | LOW1.4 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2015-3276 | LOW1.4 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW1.4 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-15719 | LOW1.4 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22185 | LOW1.4 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2015-3276 | LOW1.4 | libldap2-dev 2.4.57+dfsg-3+deb11u1 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW1.4 | libldap2-dev 2.4.57+dfsg-3+deb11u1 No fix yet | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-15719 | LOW1.4 | libldap2-dev 2.4.57+dfsg-3+deb11u1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22185 | LOW1.4 | libldap2-dev 2.4.57+dfsg-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-41409 | LOW1.4 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | LOW1.4 | libsqlite3-0 3.34.1-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | mount 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6297 | LOW1.27 | dpkg 1.20.12 fixed in 1.20.14 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-27587 | LOW1.27 | openssl 1.1.1n-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | bsdutils 1:2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libblkid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-14159 | LOW1.19 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2017-14159 | LOW1.19 | libldap2-dev 2.4.57+dfsg-3+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libmount1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libsmartcols1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-29088 | LOW1.19 | libsqlite3-0 3.34.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libuuid1 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | mount 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | util-linux 2.36.1-8+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89162 | LOW1.19 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.19 | libsqlite3-0 3.34.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libncursesw6 6.2+20201114-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libtinfo6 6.2+20201114-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-base 6.2+20201114-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-bin 6.2+20201114-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| DLA-4485-1 | NONE0 | ca-certificates 20210119 fixed in 20230311+deb12u1~deb11u1 | — | Not Applicable |
| DLA-4726-1 | NONE0 | ca-certificates 20210119 fixed in 20250419~deb12u1~deb11u1 | — | Not Applicable |
| DLA-3972-1 | NONE0 | tzdata 2021a-1+deb11u10 fixed in 2024b-0+deb11u1 | — | Not Applicable |
| DLA-4085-1 | NONE0 | tzdata 2021a-1+deb11u10 fixed in 2025a-0+deb11u1 | — | Not Applicable |
| DLA-4105-1 | NONE0 | tzdata 2021a-1+deb11u10 fixed in 2025b-0+deb11u1 | — | Not Applicable |
| DLA-4403-1 | NONE0 | tzdata 2021a-1+deb11u10 fixed in 2025b-0+deb11u2 | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2021a-1+deb11u10 fixed in 2026b-0+deb11u1 | — | Not Applicable |
| CVE-2026-105712 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.