Last scanned:
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, bypass authentication, or disrupt service availability by exploiting vulnerabilities like CVE-2022-25235 (libexpat), CVE-2026-42010 (gnutls), and CVE-2023-44487 (HTTP/2). Disabling HTTP/2 would mitigate the DDoS risk, but core library flaws require patching. Note that CVE-2026-42010 only applies if the server uses RSA-PSK cipher suites.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2022-24963 | CRITICAL9.8 | libapr1 1.7.0-6+deb11u1 fixed in 1.7.0-6+deb11u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25235 | CRITICAL9.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u2 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25315 | CRITICAL9.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u2 | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45491 | CRITICAL9.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45492 | CRITICAL9.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u6 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | CRITICAL9.8 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-56171 | CRITICAL9.8 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g 1:1.2.11.dfsg-2 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-44487 | CRITICAL9.75 | libnghttp2-14 1.43.0-1 fixed in 1.43.0-1+deb11u1 | 100.0% Actively Exploited | Directly Exposed |
| CVE-2022-0778 | CRITICAL9.75 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1k-1+deb11u2 | 70.6% Actively Exploited | Directly Exposed |
| CVE-2018-25032 | CRITICAL9.75 | zlib1g 1:1.2.11.dfsg-2 fixed in 1:1.2.11.dfsg-2+deb11u1 | 52.1% Actively Exploited | Directly Exposed |
| CVE-2023-0286 | CRITICAL9.62 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u4 | 59.5% Actively Exploited | Directly Exposed |
| CVE-2022-1292 | CRITICAL9.49 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u2 | 83.2% Actively Exploited | Directly Exposed |
| CVE-2022-2068 | CRITICAL9.49 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u3 | 95.8% Actively Exploited | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-37371 | CRITICAL9.1 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1586 | CRITICAL9.1 | libpcre2-8-0 10.36-2 fixed in 10.36-2+deb11u1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1587 | CRITICAL9.1 | libpcre2-8-0 10.36-2 fixed in 10.36-2+deb11u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46848 | CRITICAL9.1 | libtasn1-6 4.16.0-2 fixed in 4.16.0-2+deb11u1 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-49796 | CRITICAL9.1 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.31-13+deb11u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.31-13+deb11u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45960 | HIGH8.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22825 | HIGH8.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22826 | HIGH8.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-22827 | HIGH8.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-42898 | HIGH8.8 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u3 | 6.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1271 | HIGH8.8 | liblzma5 5.2.5-2 fixed in 5.2.5-2.1~deb11u1 | 4.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl2-2 2.1.27+dfsg-2.1 fixed in 2.1.27+dfsg-2.1+deb11u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-24407 | HIGH8.8 | libsasl2-modules-db 2.1.27+dfsg-2.1 fixed in 2.1.27+dfsg-2.1+deb11u1 | 4.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4450 | HIGH8.62 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u4 | 20.4% High Exploitation Risk | Directly Exposed |
| CVE-2022-40303 | HIGH8.62 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u3 | 22.8% High Exploitation Risk | Directly Exposed |
| CVE-2023-2650 | HIGH8.45 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u5 | 73.5% Actively Exploited | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.10+dfsg-6.7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40674 | HIGH8.1 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u8 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25236 | HIGH8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u2 | 34.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-37434 | HIGH8 | zlib1g 1:1.2.11.dfsg-2 fixed in 1:1.2.11.dfsg-2+deb11u2 | 16.0% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22822 | HIGH7.84 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 4.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22823 | HIGH7.84 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 3.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-22824 | HIGH7.84 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 3.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-23852 | HIGH7.84 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 4.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2013-0340 | HIGH7.82 | libexpat1 2.2.10-2 No fix yet | 19.4% High Exploitation Risk | Directly Exposed |
| CVE-2021-46143 | HIGH7.8 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre3 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-40304 | HIGH7.8 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u3 | 6.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33599 | HIGH7.6 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.31-13+deb11u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.31-13+deb11u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43396 | HIGH7.5 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.31-13+deb11u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.31-13+deb11u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43396 | HIGH7.5 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23990 | HIGH7.5 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u1 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25314 | HIGH7.5 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u2 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-43680 | HIGH7.5 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u5 | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52425 | HIGH7.5 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u6 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | HIGH7.5 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u6 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | libexpat1 2.2.10-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.2.10-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33560 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-43618 | HIGH7.5 | libgmp10 2:6.2.1+dfsg-1 fixed in 2:6.2.1+dfsg-1+deb11u1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2509 | HIGH7.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u2 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0553 | HIGH7.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0567 | HIGH7.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.18.3-6+deb11u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.18.3-6+deb11u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.18.3-6+deb11u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.18.3-6+deb11u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-common 2.4.57+dfsg-3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-common 2.4.57+dfsg-3 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-common 2.4.57+dfsg-3 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0215 | HIGH7.5 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u4 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0464 | HIGH7.5 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u5 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u7 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2309 | HIGH7.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u5 | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-23308 | HIGH7.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-25062 | HIGH7.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-27113 | HIGH7.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0361 | HIGH7.4 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u3 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-28182 | MEDIUM6.89 | libnghttp2-14 1.43.0-1 fixed in 1.43.0-1+deb11u2 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u4 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3999 | MEDIUM6.63 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.2.10-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49043 | MEDIUM6.63 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.10+dfsg-6.7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-24928 | MEDIUM6.54 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | libaprutil1 1.6.1-5 fixed in 1.6.1-5+deb11u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25147 | MEDIUM6.5 | libaprutil1-ldap 1.6.1-5 fixed in 1.6.1-5+deb11u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25313 | MEDIUM6.5 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u2 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4209 | MEDIUM6.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u4 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u4 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u4 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-36054 | MEDIUM6.5 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u4 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-29824 | MEDIUM6.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u2 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-28484 | MEDIUM6.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-29469 | MEDIUM6.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u4 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.2.10-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-37370 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u5 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.43.0-1 fixed in 1.43.0-1+deb11u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.36-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32414 | MEDIUM6.38 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32415 | MEDIUM6.38 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4802 | MEDIUM5.95 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u13 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-5222 | MEDIUM5.95 | libicu67 67.1-7 fixed in 67.1-7+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u7 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5981 | MEDIUM5.9 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.18.3-6+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-4160 | MEDIUM5.9 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1k-1+deb11u2 | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u2 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.4-2 2.4.57+dfsg-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-common 2.4.57+dfsg-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u2 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-24528 | MEDIUM5.52 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-39615 | MEDIUM5.52 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-45322 | MEDIUM5.52 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u2 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.31-13+deb11u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33600 | MEDIUM5.3 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.2.10-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12243 | MEDIUM5.3 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u7 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-2097 | MEDIUM5.3 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u4 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1n-0+deb11u5 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1v-0~deb11u1 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1v-0~deb11u1 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u2 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-12133 | MEDIUM5.3 | libtasn1-6 4.16.0-2 fixed in 4.16.0-2+deb11u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.23.22-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2016-3709 | MEDIUM5.18 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-43551 | MEDIUM5.17 | libcurl4 7.74.0-1.3+b1 No fix yet | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | MEDIUM5.17 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u12 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2026-57432 | MEDIUM5.04 | perl-base 5.32.1-4+deb11u2 No fix yet | — | Post-Exploit |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.2.10-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-3576 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u1 fixed in 1.18.3-6+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | MEDIUM5 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-22576 | MEDIUM4.86 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31484 | MEDIUM4.86 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u4 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-base 5.32.1-4+deb11u2 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | MEDIUM4.81 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u2 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2022-1304 | MEDIUM4.68 | e2fsprogs 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-49582 | MEDIUM4.67 | libapr1 1.7.0-6+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-0395 | MEDIUM4.67 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u12 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.2.10-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.2.10-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.2.10-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.11.dfsg-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-23914 | MEDIUM4.64 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.9.0-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u10 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2022-29155 | MEDIUM4.58 | libldap-2.4-2 2.4.57+dfsg-3 fixed in 2.4.57+dfsg-3+deb11u1 | 69.9% Actively Exploited | Post-Exploit |
| CVE-2022-29155 | MEDIUM4.58 | libldap-common 2.4.57+dfsg-3 fixed in 2.4.57+dfsg-3+deb11u1 | 69.9% Actively Exploited | Post-Exploit |
| CVE-2021-22946 | MEDIUM4.5 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27775 | MEDIUM4.5 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27781 | MEDIUM4.5 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-27782 | MEDIUM4.5 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-42916 | MEDIUM4.5 | libcurl4 7.74.0-1.3+b1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-28834 | MEDIUM4.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-32206 | MEDIUM4.48 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 32.0% High Exploitation Risk | Post-Exploit |
| CVE-2024-7264 | MEDIUM4.48 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u13 | 17.3% High Exploitation Risk | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-28835 | MEDIUM4.25 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1 1.9.0-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.4-2 2.4.57+dfsg-3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-common 2.4.57+dfsg-3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2024-2961 | MEDIUM4.12 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u9 | 88.3% Actively Exploited | Post-Exploit |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.4-2 2.4.57+dfsg-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-common 2.4.57+dfsg-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.31-13+deb11u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-33601 | MEDIUM4 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+b3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-16156 | LOW3.98 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-47038 | LOW3.98 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-27776 | LOW3.9 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW3.9 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u7 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW3.9 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u11 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl4 7.74.0-1.3+b1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.74.0-1.3+b1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22922 | LOW3.9 | libcurl4 7.74.0-1.3+b1 No fix yet | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-22218 | LOW3.82 | libssh2-1 1.9.0-2 fixed in 1.9.0-2+deb11u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1 1.9.0-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW3.7 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u2 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4911 | LOW3.65 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u7 | 81.4% Actively Exploited | Post-Exploit |
| CVE-2023-4911 | LOW3.65 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u7 | 81.4% Actively Exploited | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-22947 | LOW3.54 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32208 | LOW3.54 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-43552 | LOW3.54 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u5 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27535 | LOW3.54 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u8 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u8 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u9 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28320 | LOW3.54 | libcurl4 7.74.0-1.3+b1 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1664 | LOW3.53 | dpkg 1.20.9 fixed in 1.20.10 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33574 | LOW3.53 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23218 | LOW3.53 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23219 | LOW3.53 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.31-13+deb11u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-33574 | LOW3.53 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23218 | LOW3.53 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 4.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-23219 | LOW3.53 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u3 | 4.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.31-13+deb11u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32207 | LOW3.53 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 6.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-32221 | LOW3.53 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u5 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-27774 | LOW3.42 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-33602 | LOW3.4 | libc-bin 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-33602 | LOW3.4 | libc6 2.31-13+deb11u2 fixed in 2.31-13+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.1-5 fixed in 3.7.1-5+deb11u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl1.1 1.1.1k-1+deb11u1 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-8096 | LOW3.31 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u14 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1 1.9.0-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u8 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48303 | LOW3.3 | tar 1.34+dfsg-1 fixed in 1.34+dfsg-1+deb11u1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22945 | LOW3.28 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.32.1-4+deb11u2 No fix yet | — | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.74.0-1.3+b1 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl4 7.74.0-1.3+b1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22923 | LOW3.18 | libcurl4 7.74.0-1.3+b1 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-1271 | LOW3.17 | gzip 1.10-4 fixed in 1.10-4+deb11u1 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u8 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u8 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.2.10-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.36.1-8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.36.1-8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.32.1-4+deb11u2 fixed in 5.32.1-4+deb11u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-32205 | LOW2.97 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 26.9% High Exploitation Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-3995 | LOW2.8 | bsdutils 1:2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-3996 | LOW2.8 | bsdutils 1:2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-3995 | LOW2.8 | mount 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-3996 | LOW2.8 | mount 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-4641 | LOW2.8 | passwd 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-3995 | LOW2.8 | util-linux 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-3996 | LOW2.8 | util-linux 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.36.1-8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.36.1-8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | bsdutils 1:2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | mount 2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28085 | LOW2.64 | util-linux 2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.36.1-8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | passwd 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.74.0-1.3+b1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22924 | LOW2.22 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 6.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-35252 | LOW2.22 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u3 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u9 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u10 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.2.10-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.10+dfsg-6.7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-22898 | LOW1.86 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u2 | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-29383 | LOW1.68 | passwd 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-39804 | LOW1.68 | tar 1.34+dfsg-1 fixed in 1.34+dfsg-1+deb11u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-8457 | NONE0 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 45.4% High Exploitation Risk | Not Applicable |
| CVE-2022-1304 | NONE0 | libcom-err2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-1304 | NONE0 | libext2fs2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-1304 | NONE0 | libss2 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-29111 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | libtinfo6 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-1304 | NONE0 | logsave 1.46.2-2 fixed in 1.46.2-2+deb11u1 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-base 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-29491 | NONE0 | ncurses-bin 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-50387 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u6 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u6 | 81.7% Actively Exploited | Not Applicable |
| CVE-2021-46828 | NONE0 | libtirpc-common 1.3.1-1 fixed in 1.3.1-1+deb11u1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2021-46828 | NONE0 | libtirpc3 1.3.1-1 fixed in 1.3.1-1+deb11u1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-50387 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u6 | 100.0% Actively Exploited | Not Applicable |
| CVE-2023-50868 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u6 | 81.7% Actively Exploited | Not Applicable |
| CVE-2026-54369 | NONE0 | libacl1 2.2.53-10 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-29458 | NONE0 | libtinfo6 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-base 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-29458 | NONE0 | ncurses-bin 6.2+20201114-2 fixed in 6.2+20201114-2+deb11u1 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-68973 | NONE0 | gpgv 2.2.27-2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-34903 | NONE0 | gpgv 2.2.27-2 fixed in 2.2.27-2+deb11u2 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54370 | NONE0 | libacl1 2.2.53-10 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-54371 | NONE0 | libattr1 1:2.4.48-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libblkid1 2.36.1-8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libmount1 2.36.1-8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-13529 | NONE0 | libsystemd0 247.3-6 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-13529 | NONE0 | libudev1 247.3-6 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-14104 | NONE0 | libuuid1 2.36.1-8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u6 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-7008 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u6 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2021-3995 | NONE0 | libblkid1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3996 | NONE0 | libblkid1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3995 | NONE0 | libmount1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3996 | NONE0 | libmount1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.4.0-9+deb11u1 fixed in 1.4.0-9+deb11u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-3995 | NONE0 | libsmartcols1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3996 | NONE0 | libsmartcols1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-3821 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4415 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-3997 | NONE0 | libudev1 247.3-6 fixed in 247.3-7 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-3821 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4415 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2021-3995 | NONE0 | libuuid1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-3996 | NONE0 | libuuid1 2.36.1-8 fixed in 2.36.1-8+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libuuid1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4641 | NONE0 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libblkid1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libmount1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 247.3-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 247.3-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 247.3-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 247.3-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 247.3-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 247.3-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | libuuid1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libuuid1 2.36.1-8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login 1:4.8.1-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-10-base 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-4039 | NONE0 | gcc-9-base 9.3.0-22 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.27-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.27-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libblkid1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libmount1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.4.0-9+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | libsystemd0 247.3-6 fixed in 247.3-7+deb11u7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-4598 | NONE0 | libudev1 247.3-6 fixed in 247.3-7+deb11u7 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libuuid1 2.36.1-8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-4235 | NONE0 | login 1:4.8.1-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-28085 | NONE0 | libblkid1 2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libmount1 2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libsmartcols1 2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-28085 | NONE0 | libuuid1 2.36.1-8 fixed in 2.36.1-8+deb11u2 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2011-3374 | NONE0 | libapt-pkg6.0 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.8.1-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.27-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-36084 | NONE0 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-36085 | NONE0 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-36086 | NONE0 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2021-36087 | NONE0 | libsepol1 3.1-1 fixed in 3.1-1+deb11u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 247.3-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 247.3-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 247.3-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 247.3-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-29383 | NONE0 | login 1:4.8.1-1 fixed in 1:4.8.1-1+deb11u1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.2+20201114-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.1-2+b3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.9 fixed in 1.20.14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.74.0-1.3+b1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| DLA-4213-1 | NONE0 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u15 | — | Not Applicable |
| DLA-4432-1 | NONE0 | libcurl4 7.74.0-1.3+b1 fixed in 7.74.0-1.3+deb11u16 | — | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.2.10-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.2.10-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| DSA-5085-2 | NONE0 | libexpat1 2.2.10-2 fixed in 2.2.10-2+deb11u3 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.43.0-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1k-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.36.1-8 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.8.1-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.36.1-8 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.32.1-4+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.32.1-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 2.96-7 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1 No fix yet | — | Not Applicable |
| DLA-3972-1 | NONE0 | tzdata 2021a-1+deb11u2 fixed in 2024b-0+deb11u1 | — | Not Applicable |
| DLA-4085-1 | NONE0 | tzdata 2021a-1+deb11u2 fixed in 2025a-0+deb11u1 | — | Not Applicable |
| DLA-4105-1 | NONE0 | tzdata 2021a-1+deb11u2 fixed in 2025b-0+deb11u1 | — | Not Applicable |
| DLA-4403-1 | NONE0 | tzdata 2021a-1+deb11u2 fixed in 2025b-0+deb11u2 | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2021a-1+deb11u2 fixed in 2026b-0+deb11u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.36.1-8 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.36.1-8 No fix yet | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.