Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit glibc (CVE-2019-1010023) or HDF5 (CVE-2018-14031) vulnerabilities to execute arbitrary code or cause denial of service, potentially leading to unauthorized access to the PostgreSQL database. However, CVE-2019-1010023 requires user interaction (running ldd on a malicious ELF), reducing its practical exploitability in server contexts. Post-exploitation issues are low severity (max 5.0) and do not increase the overall risk.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-40633 | HIGH8.8 | libgif7 5.1.9-2+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14031 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14033 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14034 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14035 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14460 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16438 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46242 | HIGH8.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14031 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14033 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14034 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14035 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-14460 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16438 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9151 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9152 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46242 | HIGH8.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9543 | HIGH8.8 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9545 | HIGH8.8 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-35737 | HIGH8.62 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 18.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-57432 | HIGH8.4 | libperl5.32 5.32.1-4+deb11u4 No fix yet | — | Directly Exposed |
| CVE-2024-32608 | HIGH8.33 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-32608 | HIGH8.33 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.10+dfsg-6.7+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32988 | HIGH8.2 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u8 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-11205 | HIGH8.1 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-11206 | HIGH8.1 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-11205 | HIGH8.1 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-11206 | HIGH8.1 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26220 | HIGH8.1 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26221 | HIGH8.1 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-26222 | HIGH8.1 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0340 | HIGH7.82 | libexpat1 2.2.10-2+deb11u7 No fix yet | 19.4% High Exploitation Risk | Directly Exposed |
| CVE-2026-47178 | HIGH7.8 | libheif1 1.11.0-1+deb11u2 No fix yet | — | 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-2026-33845 | HIGH7.73 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-49794 | HIGH7.73 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | libexpat1 2.2.10-2+deb11u7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.2.10-2+deb11u7 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-2026-33846 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37501 | HIGH7.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-37501 | HIGH7.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20006 | HIGH7.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31598 | HIGH7.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0880 | HIGH7.5 | libxerces-c3.2 3.2.3+debian-3+deb11u1 No fix yet | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6021 | HIGH7.5 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-7424 | HIGH7.5 | libxslt1.1 1.1.34-4+deb11u2 fixed in 1.1.34-4+deb11u3 | 1.2% 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-2020-18232 | HIGH7.48 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2020-18232 | HIGH7.48 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2020-18494 | HIGH7.48 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-49463 | HIGH7.48 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-4048 | HIGH7.28 | libblas3 3.9.0-3+deb11u1 No fix yet | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-4048 | HIGH7.28 | liblapack3 3.9.0-3+deb11u1 No fix yet | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-49796 | HIGH7.28 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2020-23922 | HIGH7.1 | libgif7 5.1.9-2+deb11u1 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2153 | MEDIUM6.88 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2020-0478 | MEDIUM6.63 | libaom0 1.0.0.errata1-3+deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31782 | MEDIUM6.63 | libfreetype6 2.10.4+dfsg-1+deb11u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-49014 | MEDIUM6.63 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8086 | MEDIUM6.63 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8087 | MEDIUM6.63 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-25942 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-25972 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-26061 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-25942 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-25972 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-26061 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-2308 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-2309 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2310 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6516 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6818 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6856 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6857 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-26200 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34734 | MEDIUM6.63 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | MEDIUM6.63 | libodbc1 2.3.6-0.1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-10118 | MEDIUM6.63 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | MEDIUM6.63 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.10+dfsg-6.7+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | MEDIUM6.63 | odbcinst1debian2 2.3.6-0.1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-17507 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17432 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17435 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17439 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8396 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8398 | MEDIUM6.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17507 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15671 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17432 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17433 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17435 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17436 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-17439 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8396 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8397 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-8398 | MEDIUM6.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-3.1+b2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20005 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20007 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20198 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20199 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20200 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20201 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20202 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-30485 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31229 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31347 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31348 | MEDIUM6.5 | libnetcdf18 1:4.7.4-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6129 | MEDIUM6.5 | libpng16-16 1.6.37-3+deb11u4 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9083 | MEDIUM6.5 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-40403 | MEDIUM6.5 | libxslt1.1 1.1.34-4+deb11u2 fixed in 1.1.34-4+deb11u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u7 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+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-6239 | MEDIUM6.38 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47251 | MEDIUM6.1 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 247.3-7+deb11u6 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 247.3-7+deb11u6 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.2.53-10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-48161 | MEDIUM6.03 | libgif7 5.1.9-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13699 | MEDIUM5.95 | libmariadb3 1:10.5.29-0+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-45993 | MEDIUM5.61 | libgif7 5.1.9-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-52885 | MEDIUM5.61 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u4 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5+deb11u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46244 | MEDIUM5.52 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46243 | MEDIUM5.52 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2021-46244 | MEDIUM5.52 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49271 | MEDIUM5.52 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-30045 | MEDIUM5.52 | libnetcdf18 1:4.7.4-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | libnss3 2:3.61-1+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-40090 | MEDIUM5.52 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-28506 | MEDIUM5.5 | libgif7 5.1.9-2+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10810 | MEDIUM5.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10811 | MEDIUM5.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10809 | MEDIUM5.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10810 | MEDIUM5.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10811 | MEDIUM5.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-10812 | MEDIUM5.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-47709 | MEDIUM5.5 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Directly Exposed |
| CVE-2021-46822 | MEDIUM5.5 | libjpeg62-turbo 1:2.0.6-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-33070 | MEDIUM5.5 | libprotobuf-c1 1.3.3-1+b2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1056 | MEDIUM5.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34402 | MEDIUM5.5 | liburiparser1 0.9.4+dfsg-1+deb11u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34403 | MEDIUM5.5 | liburiparser1 0.9.4+dfsg-1+deb11u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-34459 | MEDIUM5.5 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u8 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.2.53-10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.4.48-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.2.10-2+deb11u7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-26197 | MEDIUM5.3 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.3 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-26197 | MEDIUM5.3 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2026-26199 | MEDIUM5.3 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | — | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.34-4+deb11u2 No fix yet | 2.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-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.37-3+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d4 0.7.1-3+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-31344 | MEDIUM5.02 | libgif7 5.1.9-2+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44904 | MEDIUM5.02 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-44905 | MEDIUM5.02 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | libperl5.32 5.32.1-4+deb11u4 fixed in 5.32.1-4+deb11u5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-52886 | MEDIUM5.02 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u3 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+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | MEDIUM5 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl 5.32.1-4+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-base 5.32.1-4+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8084 | MEDIUM4.67 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8088 | MEDIUM4.67 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8212 | MEDIUM4.67 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8213 | MEDIUM4.67 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39742 | MEDIUM4.67 | libgif7 5.1.9-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45830 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45833 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45829 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45830 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45832 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-45833 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2915 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2924 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2925 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2926 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6858 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7067 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7068 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7069 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29043 | MEDIUM4.67 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.37-3+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48468 | MEDIUM4.67 | libprotobuf-c1 1.3.3-1+b2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-30775 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.34-4+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-23914 | MEDIUM4.64 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.43.0-1+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-42916 | MEDIUM4.5 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2022-4899 | MEDIUM4.5 | zstd 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2912 | MEDIUM4.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-2913 | MEDIUM4.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6269 | MEDIUM4.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6270 | MEDIUM4.5 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.37-3+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44927 | MEDIUM4.5 | liburiparser1 0.9.4+dfsg-1+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44928 | MEDIUM4.5 | liburiparser1 0.9.4+dfsg-1+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42371 | MEDIUM4.33 | liburiparser1 0.9.4+dfsg-1+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.37-3+deb11u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.6% Theoretical Threat | 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 | libgfortran5 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libquadmath0 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-2019-8457 | MEDIUM4.06 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libsystemd0 247.3-7+deb11u6 fixed in 247.3-7+deb11u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4598 | MEDIUM4 | libudev1 247.3-7+deb11u6 fixed in 247.3-7+deb11u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-1013 | LOW3.98 | odbcinst 2.3.6-0.1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22922 | LOW3.9 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.4% 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-2023-6135 | LOW3.65 | libnss3 2:3.61-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6965 | LOW3.61 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 73.5% Actively Exploited | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1+deb11u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | dirmngr 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gnupg-utils 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-agent 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-wks-client 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpg-wks-server 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgconf 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgsm 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68973 | LOW3.57 | gpgv 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-31852 | LOW3.57 | libllvm16 1:16.0.6-15~deb11u2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-28320 | LOW3.54 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6879 | LOW3.53 | libaom0 1.0.0.errata1-3+deb11u2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u10 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-13869 | LOW3.53 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-13870 | LOW3.53 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-13869 | LOW3.53 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-13870 | LOW3.53 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.1-5+deb11u7 fixed in 3.7.1-5+deb11u9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-43718 | LOW3.4 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl1.1 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | LOW3.36 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u4 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.32.1-4+deb11u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | libperl5.32 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22923 | LOW3.18 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2016-9580 | LOW3.17 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2016-9581 | LOW3.17 | libopenjp2-7 2.4.0-3+deb11u3 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-2814 | LOW3.17 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2017-2818 | LOW3.17 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2017-2820 | LOW3.17 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 4.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm16 1:16.0.6-15~deb11u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.10+dfsg-6.7+deb11u7 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+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-43551 | LOW3.1 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-base 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | — | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl 5.32.1-4+deb11u4 fixed in 5.32.1-4+deb11u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.32.1-4+deb11u4 fixed in 5.32.1-4+deb11u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-modules-5.32 5.32.1-4+deb11u4 fixed in 5.32.1-4+deb11u5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-2914 | LOW2.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2914 | LOW2.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6750 | LOW2.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6816 | LOW2.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6817 | LOW2.8 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4472 | LOW2.8 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-43903 | LOW2.8 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 247.3-7+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.10+dfsg-6.7+deb11u7 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+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.64 | coreutils 8.32-4+b1 No fix yet | — | Post-Exploit |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.34-4+deb11u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | LOW2.55 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-67899 | LOW2.46 | liburiparser1 0.9.4+dfsg-1+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | login 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl3-gnutls 7.74.0-1.3+deb11u16 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-2026-24515 | LOW2.12 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6170 | LOW2.12 | libxml2 2.9.10+dfsg-6.7+deb11u7 fixed in 2.9.10+dfsg-6.7+deb11u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 1.1.1w-0+deb11u3 fixed in 1.1.1w-0+deb11u5 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.18.2 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-0861 | NONE0 | libc-l10n 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | locales 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-49014 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8086 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8087 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | 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-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-30580 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.18.2 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.18.2 fixed in 1.18.6, 1.19.1 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-29804 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30634 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.18.2 fixed in 1.17.13, 1.18.5 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.18.2 fixed in 1.18.8, 1.19.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.18.2 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.18.2 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.18.2 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-68973 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 fixed in 2.2.27-2+deb11u3 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-13699 | NONE0 | mariadb-common 1:10.5.29-0+deb11u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.18.2 fixed in 1.19.11, 1.20.6 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4806 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc-l10n 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-4806 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-4813 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | locales 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.18.2 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8084 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8088 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8212 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8213 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.3% 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-2022-1962 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.18.2 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | libc-l10n 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc-l10n 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-0915 | NONE0 | locales 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | locales 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 5.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.18.2 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.18.2 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.18.2 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.18.2 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.18.2 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.18.2 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 0.3% 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 | 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 |
| 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-2025-22870 | NONE0 | stdlib v1.18.2 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | libc-l10n 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | locales 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-l10n 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | locales 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.27-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-30629 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.1-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-56391 | NONE0 | coreutils 8.32-4+b1 No fix yet | — | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.7-5 No fix yet | — | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.13 fixed in 1.20.14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-4738 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-29480 | NONE0 | gdal-data 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3-gnutls 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45382 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-45383 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-49295 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49337 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-49346 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-54240 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-54241 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | — | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.11-0+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4738 | NONE0 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-29480 | NONE0 | libgdal28 3.2.2+dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29157 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29158 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29159 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29160 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29161 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29162 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29163 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29164 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29165 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29166 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32605 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32606 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32607 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32609 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-32610 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32611 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-32612 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-32613 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32614 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32615 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-32616 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-32617 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-32618 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32619 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32620 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32621 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32622 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-32623 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32624 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-33873 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-33874 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-33875 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33876 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33877 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-103-1 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-29157 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29158 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29159 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29160 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29161 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29162 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29163 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29164 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-29165 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-29166 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32605 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32606 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32607 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32609 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-32610 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32611 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-32612 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-32613 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32614 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32615 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2024-32616 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-32617 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-32618 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32619 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32620 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-32621 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32622 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-32623 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-32624 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-33873 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-33874 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-33875 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33876 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-33877 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-2923 | NONE0 | libhdf5-hl-100 1.10.6+repack-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41069 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-47247 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-47254 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-47714 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-48029 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-50142 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | — | Not Applicable |
| CVE-2024-25269 | NONE0 | libheif1 1.11.0-1+deb11u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.12~rc1-2+deb11u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2025-14932 | NONE0 | libnetcdf18 1:4.7.4-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14933 | NONE0 | libnetcdf18 1:4.7.4-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14934 | NONE0 | libnetcdf18 1:4.7.4-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14935 | NONE0 | libnetcdf18 1:4.7.4-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14936 | NONE0 | libnetcdf18 1:4.7.4-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16389 | NONE0 | libnss3 2:3.61-1+deb11u6 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.32 5.32.1-4+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.32 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40930 | NONE0 | libpng16-16 1.6.37-3+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-50420 | NONE0 | libpoppler102 20.09.0-3.1+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66032 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-66033 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-66034 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-66035 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1w-0+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff5 4.2.0-1+deb11u8 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 1.1.1w-0+deb11u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.32.1-4+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.32.1-4+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.32 5.32.1-4+deb11u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 2.96-7+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1+deb11u1 No fix yet | — | Not Applicable |
| DLA-4403-1 | NONE0 | tzdata 2025b-0+deb11u1 fixed in 2025b-0+deb11u2 | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2025b-0+deb11u1 fixed in 2026b-0+deb11u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-39824 | NONE0 | golang.org/x/sys v0.13.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.