Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who can reach the web front end or the realtime socket server could take the ERPNext site offline or crash its realtime service through CVE-2023-44487 and CVE-2024-37890. Note: CVE-2024-37890 and the other ws findings come from a copy of the ws package used by socket.io, and the libxml2 findings only matter if the application parses attacker-supplied XML through libxml2 or its Python bindings. The scan also found 794 exposed findings in total, so the remaining exposure should be patched before production use.
Hardening plan for this image · 4 steps. The first targets an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH7.84 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-37890 | HIGH7.5 | ws 8.11.0 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-48779 | HIGH7.5 | ws 8.11.0 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 1.4% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-93479 | HIGH7 | nginx 1.22.1-9+deb12u10 No fix yet | 1.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-93479 | HIGH7 | nginx-common 1.22.1-9+deb12u10 No fix yet | 1.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-74860 | MEDIUM6.8 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26240 | MEDIUM6.72 | pdfkit 1.0.0 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6238 | MEDIUM6.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93541 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93542 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93543 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93544 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93545 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94281 | MEDIUM6.5 | libxi6 2:1.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97629 | MEDIUM6.5 | nginx 1.22.1-9+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-97629 | MEDIUM6.5 | nginx-common 1.22.1-9+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-15176 | MEDIUM6.48 | nginx 1.22.1-9+deb12u10 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97205 | MEDIUM6.48 | nginx 1.22.1-9+deb12u10 No fix yet | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-15176 | MEDIUM6.48 | nginx-common 1.22.1-9+deb12u10 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97205 | MEDIUM6.48 | nginx-common 1.22.1-9+deb12u10 No fix yet | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54371 | MEDIUM6.3 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86140 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86142 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86144 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13757 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.16 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-90781 | MEDIUM6.1 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90781 | MEDIUM6.1 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94282 | MEDIUM6.1 | libxi6 2:1.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3163 | MEDIUM6.1 | quill 1.3.7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-15056 | MEDIUM6.1 | quill 2.0.3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59710 | MEDIUM6.1 | showdown 2.1.0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59711 | MEDIUM6.1 | showdown 2.1.0 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM6.1 | python 3.11.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-25193 | MEDIUM6 | libharfbuzz-subset0 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-25193 | MEDIUM6 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-2391 | MEDIUM6 | qs 6.11.2 fixed in 6.14.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-33151 | MEDIUM6 | socket.io-parser 4.2.4 fixed in 3.3.5, 3.4.4, 4.2.6 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69185 | MEDIUM6 | socket.io-parser 4.2.4 fixed in 4.2.7, 3.4.5, 3.3.6 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-45736 | MEDIUM6 | ws 8.11.0 fixed in 8.20.1 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM6 | python 3.11.18 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM6 | python 3.11.18 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-73086 | MEDIUM5.92 | nanoid 3.3.7 fixed in 3.3.12, 5.1.11 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | MEDIUM5.9 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-17495 | MEDIUM5.9 | moment 2.30.1 fixed in 2.31.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45853 | MEDIUM5.88 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4800 | MEDIUM5.88 | lodash 4.17.21 fixed in 4.18.0 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4800 | MEDIUM5.88 | lodash-es 4.17.21 fixed in 4.18.0 | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2024-36361 | MEDIUM5.78 | pug 3.0.2 fixed in 3.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-36361 | MEDIUM5.78 | pug-code-gen 3.0.2 fixed in 3.0.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.6 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-5388 | MEDIUM5.52 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | MEDIUM5.52 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM5.5 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype6 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4367 | MEDIUM5.5 | libxpm4 1:3.5.12-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94287 | MEDIUM5.5 | libxpm4 1:3.5.12-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python 3.11.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | MEDIUM5.46 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45623 | MEDIUM5.46 | postcss 5.2.18 fixed in 8.5.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45623 | MEDIUM5.46 | postcss 6.0.23 fixed in 8.5.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45623 | MEDIUM5.46 | postcss 7.0.39 fixed in 8.5.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45623 | MEDIUM5.46 | postcss 8.4.31 fixed in 8.5.12 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM5.4 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc3 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95101 | MEDIUM5.3 | nginx 1.22.1-9+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-95101 | MEDIUM5.3 | nginx-common 1.22.1-9+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-85062 | MEDIUM5.3 | colord 2.9.3 fixed in 2.9.4 | 0.5% Theoretical Threat | Directly Exposed |
| GHSA-67mh-4wv8-2f99 | MEDIUM5.3 | esbuild 0.14.54 fixed in 0.25.0 | — | Directly Exposed |
| CVE-2024-4067 | MEDIUM5.3 | micromatch 4.0.5 fixed in 4.0.8 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-12084 | MEDIUM5.3 | python 3.11.18 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python 3.11.18 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-46175 | MEDIUM5.28 | json5 0.5.1 fixed in 2.2.2, 1.0.2 | 9.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-112942 | MEDIUM5.28 | launch-editor 2.6.1 fixed in 2.14.2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-47273 | MEDIUM5.28 | setuptools 70.3.0 fixed in 78.1.1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58014 | MEDIUM5.16 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.07 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2023-44487 | MEDIUM5.07 | nginx 1.22.1-9+deb12u10 No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2023-44487 | MEDIUM5.07 | nginx-common 1.22.1-9+deb12u10 No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-107818 | MEDIUM5.04 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | MEDIUM4.98 | libxrender1 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52011 | MEDIUM4.98 | launch-editor 2.6.1 fixed in 2.9.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.92 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM4.92 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM4.92 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM4.92 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73650 | MEDIUM4.92 | svgo 2.8.0 fixed in 2.8.3, 3.3.4, 4.0.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-84370 | MEDIUM4.92 | svgo 2.8.0 fixed in 2.8.4, 3.3.5, 4.1.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44705 | MEDIUM4.92 | tmp 0.2.1 fixed in 0.2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-112943 | MEDIUM4.86 | launch-editor 2.6.1 fixed in 2.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9277 | MEDIUM4.86 | shell-quote 1.8.1 fixed in 1.8.4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM4.68 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28417 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28421 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39881 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43961 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52858 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52860 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55693 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55895 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57455 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57456 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59856 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59858 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73073 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73076 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73077 | MEDIUM4.68 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28417 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28421 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39881 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43961 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52858 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52860 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55693 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55895 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57455 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57456 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59856 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59858 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73073 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73076 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73077 | MEDIUM4.68 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | MEDIUM4.64 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8927 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-2953 | MEDIUM4.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26269 | MEDIUM4.5 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26269 | MEDIUM4.5 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102278 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14257 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-69152 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM4.5 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12143 | MEDIUM4.5 | form-data 4.0.0 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-67213 | MEDIUM4.5 | nanoid 3.3.7 fixed in 3.3.18, 5.1.6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-67214 | MEDIUM4.5 | nanoid 3.3.7 fixed in 3.3.16, 5.1.16 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-73646 | MEDIUM4.5 | postcss 5.2.18 fixed in 8.5.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-23382 | MEDIUM4.5 | postcss 5.2.18 fixed in 8.2.13, 7.0.36 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73646 | MEDIUM4.5 | postcss 6.0.23 fixed in 8.5.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-23382 | MEDIUM4.5 | postcss 6.0.23 fixed in 8.2.13, 7.0.36 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73646 | MEDIUM4.5 | postcss 7.0.39 fixed in 8.5.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73646 | MEDIUM4.5 | postcss 8.4.31 fixed in 8.5.18 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13311 | MEDIUM4.5 | shell-quote 1.8.1 fixed in 1.9.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29074 | MEDIUM4.5 | svgo 2.8.0 fixed in 2.8.1, 3.3.3, 4.0.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-1899 | MEDIUM4.5 | showdown 2.1.0 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2009-4487 | MEDIUM4.48 | nginx 1.22.1-9+deb12u10 No fix yet | 26.8% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2009-4487 | MEDIUM4.48 | nginx-common 1.22.1-9+deb12u10 No fix yet | 26.8% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-96674 | MEDIUM4.4 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96674 | MEDIUM4.4 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | MEDIUM4.38 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73072 | MEDIUM4.38 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25749 | MEDIUM4.38 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41411 | MEDIUM4.38 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | MEDIUM4.38 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73072 | MEDIUM4.38 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25749 | MEDIUM4.38 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41411 | MEDIUM4.38 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| GHSA-g2v6-rqmx-r4w6 | MEDIUM4.32 | @vue/server-renderer 3.3.9 fixed in 3.5.42, 3.6.0-rc.6 | — | Directly Exposed |
| CVE-2026-25068 | MEDIUM4.3 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | MEDIUM4.3 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33532 | MEDIUM4.3 | yaml 1.10.2 fixed in 2.8.3, 1.10.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.26 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35177 | MEDIUM4.26 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35177 | MEDIUM4.26 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.24 | libharfbuzz-subset0 6.0.0+dfsg-3 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-22693 | MEDIUM4.24 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-82417 | MEDIUM4.24 | qs 6.11.2 fixed in 6.16.0 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-8723 | MEDIUM4.24 | qs 6.11.2 fixed in 6.15.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46483 | MEDIUM4.2 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46483 | MEDIUM4.2 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73074 | MEDIUM4.02 | vim 2:9.0.1378-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73074 | MEDIUM4.02 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-112944 | MEDIUM4.02 | launch-editor 2.6.1 fixed in 2.14.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-115506 | MEDIUM4 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107080 | MEDIUM4 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-39824 | MEDIUM4 | golang.org/x/sys v0.0.0-20220715151400-c0bba94af5f8 fixed in 0.44.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8924 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libncurses6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libncursesw6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13346 | LOW3.9 | pip 24.0 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-56109 | LOW3.9 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56109 | LOW3.9 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40612 | LOW3.9 | libjq1 1.6-2.1+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28162 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-2663 | LOW3.9 | libxtables12 1.8.9-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0337 | LOW3.9 | nginx 1.22.1-9+deb12u10 No fix yet | 2.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2013-0337 | LOW3.9 | nginx-common 1.22.1-9+deb12u10 No fix yet | 2.2% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-107822 | LOW3.84 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.7 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41305 | LOW3.66 | postcss 5.2.18 fixed in 8.5.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41305 | LOW3.66 | postcss 6.0.23 fixed in 8.5.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41305 | LOW3.66 | postcss 7.0.39 fixed in 8.5.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41305 | LOW3.66 | postcss 8.4.31 fixed in 8.5.10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-84369 | LOW3.66 | svgo 2.8.0 fixed in 2.8.4, 3.3.5, 4.1.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | LOW3.66 | setuptools 70.3.0 fixed in 83.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-104844 | LOW3.54 | postcss-selector-parser 6.0.13 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-29063 | LOW3.53 | immutable 4.3.4 fixed in 4.3.8, 5.1.5, 3.8.3 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-37601 | LOW3.53 | loader-utils 0.2.17 fixed in 2.0.3, 1.4.1 | 3.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW3.48 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW3.42 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | LOW3.31 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-29481 | LOW3.31 | libbpf1 1:1.1.2-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | LOW3.31 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-23337 | LOW3.31 | libjq1 1.6-2.1+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | LOW3.31 | libjq1 1.6-2.1+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-26924 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-29932 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29933 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29934 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29935 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29939 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29941 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29942 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-31852 | LOW3.31 | libllvm15 1:15.0.6-4+b1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | LOW3.31 | libpixman-1-0 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | LOW3.31 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88372 | LOW3.3 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88386 | LOW3.3 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | LOW3.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | LOW3.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW3.3 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45130 | LOW3.3 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55892 | LOW3.3 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59857 | LOW3.3 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73070 | LOW3.3 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28418 | LOW3.3 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45130 | LOW3.3 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55892 | LOW3.3 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59857 | LOW3.3 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73070 | LOW3.3 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | LOW3.3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8643 | LOW3.3 | pip 24.0 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW3.3 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python 3.11.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW3.3 | python 3.11.18 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48758 | LOW3.24 | @sigstore/core 2.0.0 fixed in 3.2.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7783 | LOW3.24 | form-data 4.0.0 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4873 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15588 | LOW3.18 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | LOW3.18 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-56226 | LOW3.18 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44656 | LOW3.18 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47167 | LOW3.18 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44656 | LOW3.18 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47167 | LOW3.18 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | LOW3.18 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | LOW3.18 | brace-expansion 1.1.11 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53632 | LOW3.18 | launch-editor 2.6.1 fixed in 2.14.1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | LOW3.18 | lodash 4.17.21 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2950 | LOW3.18 | lodash 4.17.21 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | LOW3.18 | lodash-es 4.17.21 fixed in 4.17.23 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-2950 | LOW3.18 | lodash-es 4.17.21 fixed in 4.18.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-69153 | LOW3.18 | postcss 5.2.18 fixed in 8.5.23 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-69153 | LOW3.18 | postcss 6.0.23 fixed in 8.5.23 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-69153 | LOW3.18 | postcss 7.0.39 fixed in 8.5.23 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-69153 | LOW3.18 | postcss 8.4.31 fixed in 8.5.23 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | LOW3.17 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-85746 | LOW3.17 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-92262 | LOW3.17 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97380 | LOW3.17 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-47162 | LOW3.17 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | LOW3.17 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | LOW3.17 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73078 | LOW3.17 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-7883 | LOW3.15 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-47764 | LOW3.15 | cookie 0.4.2 fixed in 0.7.0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | LOW3.12 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69192 | LOW3.1 | ip-address 10.1.0 fixed in 10.3.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | LOW3.06 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-xcb1 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | LOW3.02 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-107818 | LOW3.02 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | LOW3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3219 | LOW3 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15284 | LOW2.96 | qs 6.11.2 fixed in 6.14.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34982 | LOW2.95 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | LOW2.95 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | LOW2.92 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-55565 | LOW2.92 | nanoid 3.3.7 fixed in 5.0.9, 3.3.8 | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.82 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57452 | LOW2.82 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57452 | LOW2.82 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | LOW2.81 | libncurses6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41992 | LOW2.7 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-48631 | LOW2.7 | @adobe/css-tools 4.3.1 fixed in 4.3.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-102276 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-102278 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-14257 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-69152 | LOW2.7 | brace-expansion 2.0.2 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33750 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-4068 | LOW2.7 | braces 3.0.2 fixed in 3.0.3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-73088 | LOW2.7 | browserslist 4.22.1 fixed in 4.28.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-73089 | LOW2.7 | browserslist 4.22.1 fixed in 4.28.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-45822 | LOW2.7 | decode-uri-component 0.2.2 fixed in 0.5.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-93748 | LOW2.7 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59879 | LOW2.7 | immutable 4.3.4 fixed in 4.3.9, 5.1.8, 3.8.4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59880 | LOW2.7 | immutable 4.3.4 fixed in 4.3.9, 5.1.8, 3.8.4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-26996 | LOW2.7 | minimatch 3.1.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-27903 | LOW2.7 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-27904 | LOW2.7 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 19.0.2 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 20.0.1 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW2.7 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW2.7 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48815 | LOW2.7 | sigstore 3.1.0 fixed in 4.1.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-93749 | LOW2.7 | source-map-js 1.0.2 fixed in 1.2.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-44270 | LOW2.7 | postcss 5.2.18 fixed in 8.4.31 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-44270 | LOW2.7 | postcss 6.0.23 fixed in 8.4.31 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-44270 | LOW2.7 | postcss 7.0.39 fixed in 8.4.31 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-54798 | LOW2.7 | tmp 0.2.1 fixed in 0.2.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8869 | LOW2.7 | pip 24.0 fixed in 25.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.65 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-27943 | LOW2.65 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-27943 | LOW2.65 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107817 | LOW2.64 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.64 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42307 | LOW2.64 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28420 | LOW2.64 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42307 | LOW2.64 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-46653 | LOW2.63 | formidable 2.1.2 fixed in 3.5.3, 2.1.3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | libmariadb3 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client-core 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-common 1:10.11.19-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | LOW2.56 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94286 | LOW2.56 | libxtst6 2:1.2.3-1.1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7709 | LOW2.55 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libgbm1 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95209 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | — | Directly Exposed |
| CVE-2026-95210 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW2.4 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-2379 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW2.34 | git 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | LOW2.34 | git 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-40612 | LOW2.34 | jq 1.6-2.1+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-0725 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | LOW2.34 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW2.34 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-109828 | LOW2.34 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW2.34 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-4677 | LOW2.34 | vim 2:9.0.1378-2+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28419 | LOW2.34 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52859 | LOW2.34 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2008-4677 | LOW2.34 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28419 | LOW2.34 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52859 | LOW2.34 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1703 | LOW2.34 | pip 24.0 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54370 | LOW2.27 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29768 | LOW2.24 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29768 | LOW2.24 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | apt 2.6.2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13608 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42338 | LOW2.2 | ip-address 10.1.0 fixed in 10.1.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-104844 | LOW2.12 | postcss-selector-parser 7.1.1 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-45913 | LOW2.12 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libgl1 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libglvnd0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libglx0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-29070 | LOW2.12 | liblcms2-2 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl-dev 3.0.22-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl3 3.0.22-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-53906 | LOW2.09 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-53906 | LOW2.09 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW1.99 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | LOW1.99 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-23337 | LOW1.99 | jq 1.6-2.1+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW1.99 | jq 1.6-2.1+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW1.99 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW1.99 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | LOW1.99 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | LOW1.99 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-1000382 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1264 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1355 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2609 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3896 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-46246 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4733 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4734 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4735 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4750 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4751 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-48231 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48232 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48233 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48234 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48235 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48236 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48237 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48706 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-5441 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-5535 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-41957 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-41965 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43374 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43790 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1215 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22134 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24014 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26603 | LOW1.99 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-1000382 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1264 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1355 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2609 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-3896 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-46246 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4733 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4734 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4735 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4750 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4751 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-48231 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48232 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48233 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48234 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48235 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48236 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-48237 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-48706 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-5441 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-5535 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-41957 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-41965 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43374 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-43790 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1215 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22134 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-24014 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26603 | LOW1.99 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW1.98 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13149 | LOW1.91 | brace-expansion 2.0.2 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102277 | LOW1.91 | brace-expansion 2.0.2 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101911 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101912 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101913 | LOW1.91 | ip-address 10.1.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-111997 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW1.91 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW1.91 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.86 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | libperl5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5889 | LOW1.58 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9358 | LOW1.55 | postcss-selector-parser 7.1.1 fixed in 6.1.3, 7.1.3 | 0.3% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.15-2+b13 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.06-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-28422 | LOW1.32 | vim 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28422 | LOW1.32 | vim-common 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW1.27 | openssl 3.0.22-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 70.3.0 fixed in 84.1.0 | — | Directly Exposed |
| CVE-2025-68121 | NONE0 | stdlib v1.19 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.19 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.19 fixed in 1.19.9, 1.20.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.19 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.19 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-73078 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73073 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-73076 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73077 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.19 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.19 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.19 fixed in 1.18.6, 1.19.1 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.19 fixed in 1.18.7, 1.19.2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.19 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-32190 | NONE0 | stdlib v1.19 fixed in 1.19.1 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.19 fixed in 1.18.7, 1.19.2 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.19 fixed in 1.18.8, 1.19.3 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.19 fixed in 1.18.9, 1.19.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.19 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.19 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.19 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.19 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.19 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.19 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.19 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.19 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.19 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.19 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.19 fixed in 1.21.9, 1.22.2 | 89.5% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.19 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.19 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.19 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.19 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.19 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.19 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.19 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.19 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.19 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.19 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.19 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-4055 | NONE0 | xdg-utils 1.1.3-4.1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-73072 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.19 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.19 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.19 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.19 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.19 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-73074 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2020-27748 | NONE0 | xdg-utils 1.1.3-4.1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.19 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.19 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.19 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.19 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.19 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-39318 | NONE0 | stdlib v1.19 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.19 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.19 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.19 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.19 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.19 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.19 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.19 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73070 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.19 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.19 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.19 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.19 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.19 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.19 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.19 fixed in 1.18.9, 1.19.4 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.19 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.19 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.19 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.19 fixed in 1.20.11, 1.21.4 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.19 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.19 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.19 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.19 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.19 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.19 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.19 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.19 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.19 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-29768 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.19 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.19 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-53905 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2008-4677 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-1000382 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1264 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-1355 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-2609 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-3896 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-46246 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4733 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4734 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4735 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4750 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-4751 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-48231 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48232 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48233 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-48234 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-48235 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-48236 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-48237 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-48706 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-5441 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-5535 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-41957 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-41965 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43374 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-43790 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1215 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22134 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-24014 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-26603 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.19 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-52968 | NONE0 | xdg-utils 1.1.3-4.1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.19 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-runtime 2:9.0.1378-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.