Last scanned:
··This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker who sends crafted compressed data to a process that decodes Brotli input could crash it or run code as the frappe user, which would disrupt the ERP service and expose the data it handles. The brotli flaw CVE-2026-111497 is the most serious item and is listed as actively exploited, but it matters only where Brotli decoding happens in this deployment. The WebSocket and GitPython issues, including CVE-2026-114145, add further exposure, and the image runs as a non-root user with no ports declared, which limits but does not remove the risk.
Hardening plan for this image · 5 steps. The first closes an actively exploited CVE.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-111497 | HIGH8 | brotli 1.0.6-4.el8_10 fixed in 1.1.0-2+deb13u1 | 82.6% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6653 | HIGH7.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 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 Exposed |
| 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 Exposed |
| CVE-2026-45736 | HIGH7.5 | ws 8.11.0 fixed in 8.20.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48779 | HIGH7.5 | ws 8.17.1 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45736 | HIGH7.5 | ws 8.17.1 fixed in 8.20.1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-54404 | HIGH7.5 | zod 4.4.3 fixed in 4.6.6 | — | Directly Exposed |
| CVE-2026-114145 | HIGH7.5 | GitPython 3.1.62 fixed in 3.2.1 | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-6v7p-g79w-8964 | HIGH7.5 | msgpack 1.1.2 fixed in 1.2.1 | — | Directly Exposed |
| GHSA-g2v6-rqmx-r4w6 | HIGH7.2 | @vue/server-renderer 3.3.9 fixed in 3.5.42, 3.6.0-rc.6 | — | Directly Exposed |
| CVE-2026-54369 | HIGH7.1 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94286 | HIGH7.1 | libxtst6 2:1.2.5-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | HIGH7 | libc-bin 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | HIGH7 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | HIGH7 | libc6 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | HIGH7 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM6.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.41-12+deb13u4 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.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM6.5 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM6.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc-common 1.3.6+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | MEDIUM6.5 | libtirpc3t64 1.3.6+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93541 | MEDIUM6.5 | libxi6 2:1.8.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93542 | MEDIUM6.5 | libxi6 2:1.8.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93543 | MEDIUM6.5 | libxi6 2:1.8.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93544 | MEDIUM6.5 | libxi6 2:1.8.2-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93545 | MEDIUM6.5 | libxi6 2:1.8.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94281 | MEDIUM6.5 | libxi6 2:1.8.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97687 | MEDIUM6.48 | urllib3 2.7.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54370 | MEDIUM6.3 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM6.3 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86139 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86140 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86142 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86144 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13757 | MEDIUM6.2 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM6.2 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.16 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libatomic1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-90781 | MEDIUM6.1 | libasound2-data 1.2.14-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90781 | MEDIUM6.1 | libasound2t64 1.2.14-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94282 | MEDIUM6.1 | libxi6 2:1.8.2-1 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-2022-29155 | MEDIUM6 | openldap 2.4.46-21.el8_10 fixed in 2.5.12+dfsg-1 | 64.5% Actively Exploited | Directly Exposed |
| 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-33151 | MEDIUM6 | socket.io-parser 4.2.5 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.5 fixed in 4.2.7, 3.4.5, 3.3.6 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97689 | MEDIUM6 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | MEDIUM5.9 | libexpat1 2.9.0-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-17495 | MEDIUM5.9 | moment 2.30.1 fixed in 2.31.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49261 | MEDIUM5.88 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49261 | MEDIUM5.88 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.6% 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-2020-36221 | MEDIUM5.85 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2020-36222 | MEDIUM5.85 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 77.2% Actively Exploited | Directly Exposed |
| CVE-2020-36227 | MEDIUM5.85 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 77.2% Actively Exploited | Directly Exposed |
| CVE-2020-36228 | MEDIUM5.85 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 85.0% Actively Exploited | Directly Exposed |
| CVE-2021-27212 | MEDIUM5.85 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-2 | 66.1% Actively Exploited | Directly Exposed |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libatomic1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | libasound2-data 1.2.14-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96675 | MEDIUM5.5 | libasound2t64 1.2.14-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM5.5 | libexpat1 2.9.0-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype6 2.13.3+dfsg-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM5.5 | libminizip1t64 1:1.3.dfsg+really1.3.1-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM5.5 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM5.5 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94287 | MEDIUM5.5 | libxpm4 1:3.5.17-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM5.5 | zlib1g 1:1.3.dfsg+really1.3.1-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-115572 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.21.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-115580 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.21.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-115585 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.21.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113789 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.21.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-113790 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.21.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-113791 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.21.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-113792 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.20.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-113793 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.20.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113794 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113795 | MEDIUM5.5 | pypdf 6.19.0 fixed in 6.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1586 | MEDIUM5.46 | pcre2 10.32-3.el8_6 fixed in 10.40-1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1587 | MEDIUM5.46 | pcre2 10.32-3.el8_6 fixed in 10.40-1 | 2.8% Low-Moderate Risk | 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.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | MEDIUM5.3 | libglib2.0-0t64 2.84.4-3~deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc-common 1.3.6+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | MEDIUM5.3 | libtirpc3t64 1.3.6+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| 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-2026-85746 | MEDIUM5.28 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73078 | MEDIUM5.28 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-73078 | MEDIUM5.28 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | 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-2026-112942 | MEDIUM5.28 | vite 8.2.1 fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4 | 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-2020-8927 | MEDIUM5.2 | brotli 1.0.6-4.el8_10 fixed in 1.0.9-1 | 3.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2020-36230 | MEDIUM5.17 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 12.1% High Exploitation Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.07 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | libminizip1t64 1:1.3.dfsg+really1.3.1-1+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-2483 | MEDIUM5 | libxcrypt 4.1.1-6.el8 fixed in 1:2.4-1.1 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib1g 1:1.3.dfsg+really1.3.1-1+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | MEDIUM4.98 | libxrender1 1:0.9.12-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-37555 | MEDIUM4.92 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM4.92 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-86145 | MEDIUM4.92 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34982 | MEDIUM4.92 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34982 | MEDIUM4.92 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101909 | MEDIUM4.92 | axios 1.18.1 fixed in 0.34.0, 1.20.0 | 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.4 fixed in 0.2.6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM4.88 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-5318 | MEDIUM4.86 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5987 | MEDIUM4.86 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 1.7% Low-Moderate Risk | 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-112943 | MEDIUM4.86 | vite 8.2.1 fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28417 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28421 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39881 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43961 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52858 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52860 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55693 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55895 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57455 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57456 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59856 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59858 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73073 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73076 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73077 | MEDIUM4.68 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28417 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28421 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39881 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43961 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52858 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52860 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55693 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-55895 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57455 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57456 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59856 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59858 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73073 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73076 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73077 | MEDIUM4.68 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | MEDIUM4.64 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-48795 | MEDIUM4.6 | libssh 0.9.6-16.el8_10 fixed in 0.10.6-1 | 93.5% Actively Exploited | Directly Exposed |
| CVE-2026-103111 | MEDIUM4.56 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg1-9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg1-9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM4.5 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM4.5 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59849 | MEDIUM4.5 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM4.5 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-6 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-data 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-xcb1 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-12243 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.50+dfsg-1 | 4.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25692 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.55+dfsg-1 | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25709 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.56+dfsg-1 | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-25710 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.56+dfsg-1 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36223 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36224 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36225 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36226 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36229 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.4.57+dfsg-1 | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | MEDIUM4.5 | openldap 2.4.46-21.el8_10 fixed in 2.5.16+dfsg-1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20454 | MEDIUM4.5 | pcre2 10.32-3.el8_6 fixed in 10.34-1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-26269 | MEDIUM4.5 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-26269 | MEDIUM4.5 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101901 | MEDIUM4.5 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101903 | MEDIUM4.5 | axios 1.18.1 fixed in 1.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101906 | MEDIUM4.5 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45819 | MEDIUM4.5 | baseline-browser-mapping 2.10.40 fixed in 2.11.0 | 0.5% 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-102276 | MEDIUM4.5 | brace-expansion 5.0.7 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 5.0.7 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 5.0.7 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 5.0.7 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102276 | MEDIUM4.5 | brace-expansion 5.0.9 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 5.0.9 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% 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-2025-5372 | MEDIUM4.49 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2009-4487 | MEDIUM4.48 | nginx 1.26.3-3+deb13u10 No fix yet | 26.8% High Exploitation Risk | Directly Exposed |
| CVE-2009-4487 | MEDIUM4.48 | nginx-common 1.26.3-3+deb13u10 No fix yet | 26.8% High Exploitation Risk | Directly Exposed |
| CVE-2026-89157 | MEDIUM4.44 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101905 | MEDIUM4.44 | axios 1.18.1 fixed in 1.20.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-96674 | MEDIUM4.4 | libasound2-data 1.2.14-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-96674 | MEDIUM4.4 | libasound2t64 1.2.14-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.38 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.38 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.38 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15370 | MEDIUM4.38 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | MEDIUM4.38 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73072 | MEDIUM4.38 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25749 | MEDIUM4.38 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41411 | MEDIUM4.38 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | MEDIUM4.38 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73072 | MEDIUM4.38 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25749 | MEDIUM4.38 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41411 | MEDIUM4.38 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.5% Low-Moderate Risk | 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-35177 | MEDIUM4.26 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-35177 | MEDIUM4.26 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | MEDIUM4.24 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46483 | MEDIUM4.2 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46483 | MEDIUM4.2 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-73074 | MEDIUM4.02 | vim 2:9.1.1230-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73074 | MEDIUM4.02 | vim-common 2:9.1.1230-2+deb13u2 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-112944 | MEDIUM4.02 | vite 8.2.1 fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-115506 | MEDIUM4 | libexpat1 2.9.0-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107080 | MEDIUM4 | libopenjp2-7 2.5.3-2.1~deb13u2 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-60585 | LOW3.96 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-1667 | LOW3.9 | libssh 0.9.6-16.el8_10 fixed in 0.10.5-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2283 | LOW3.9 | libssh 0.9.6-16.el8_10 fixed in 0.10.5-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5449 | LOW3.9 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59843 | LOW3.9 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | LOW3.9 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-6 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-data 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-xcb1 2:1.8.12-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89158 | LOW3.9 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89160 | LOW3.9 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101907 | LOW3.9 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101899 | LOW3.9 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101900 | LOW3.9 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101904 | LOW3.9 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-101908 | LOW3.9 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56109 | LOW3.9 | libasound2-data 1.2.14-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56109 | LOW3.9 | libasound2t64 1.2.14-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | LOW3.9 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW3.9 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | LOW3.9 | libglib2.0-0t64 2.84.4-3~deb13u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW3.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW3.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW3.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | LOW3.9 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3713 | LOW3.9 | libpng16-16t64 1.6.48-1+deb13u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.9 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | LOW3.9 | libxtables12 1.8.11-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0337 | LOW3.9 | nginx 1.26.3-3+deb13u10 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0337 | LOW3.9 | nginx-common 1.26.3-3+deb13u10 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | LOW3.78 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.4 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.41-12+deb13u4 No fix yet | 0.3% 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-112945 | LOW3.66 | vite 8.2.1 fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4 | 0.7% 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-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | LOW3.54 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | LOW3.54 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-101902 | LOW3.54 | axios 1.18.1 fixed in 0.34.0, 1.20.0 | 0.4% 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-49261 | LOW3.53 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-49261 | LOW3.53 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| 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-15534 | LOW3.42 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | LOW3.31 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | LOW3.31 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | LOW3.31 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | LOW3.31 | libjq1 1.7.1-6+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW3.31 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | LOW3.31 | libnss3 2:3.110-1+deb13u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | LOW3.31 | libnss3 2:3.110-1+deb13u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | LOW3.31 | libnss3 2:3.110-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | LOW3.31 | libnss3 2:3.110-1+deb13u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | LOW3.31 | libpixman-1-0 0.44.0-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | LOW3.31 | libpng16-16t64 1.6.48-1+deb13u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88372 | LOW3.3 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88386 | LOW3.3 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | LOW3.3 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-6 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-data 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-xcb1 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.35+dfsg-3.1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW3.3 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45130 | LOW3.3 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55892 | LOW3.3 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59857 | LOW3.3 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73070 | LOW3.3 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28418 | LOW3.3 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45130 | LOW3.3 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55892 | LOW3.3 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59857 | LOW3.3 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73070 | LOW3.3 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW3.3 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW3.3 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW3.3 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-113786 | LOW3.3 | pypdf 6.19.0 fixed in 6.21.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6918 | LOW3.18 | libssh 0.9.6-16.el8_10 fixed in 0.10.6-1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59848 | LOW3.18 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44656 | LOW3.18 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47167 | LOW3.18 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44656 | LOW3.18 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-47167 | LOW3.18 | vim-common 2:9.1.1230-2+deb13u2 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-102277 | LOW3.18 | brace-expansion 5.0.7 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102277 | LOW3.18 | brace-expansion 5.0.9 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-101910 | LOW3.18 | ip-address 10.5.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101911 | LOW3.18 | ip-address 10.5.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101912 | LOW3.18 | ip-address 10.5.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101913 | LOW3.18 | ip-address 10.5.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-111997 | LOW3.18 | ip-address 10.5.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Post-Exploit |
| 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-112947 | LOW3.18 | vite 8.2.1 fixed in 8.3.3, 8.2.4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47162 | LOW3.17 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | LOW3.17 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-7883 | LOW3.15 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | LOW3.12 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-94285 | LOW3.06 | libx11-6 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-data 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-xcb1 2:1.8.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | LOW2.92 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.88 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-101898 | LOW2.88 | axios 1.18.1 fixed in 1.20.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.82 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg 2.4.7-21+deb13u1+b5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgconf 2.4.7-21+deb13u1+b5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-57452 | LOW2.82 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57452 | LOW2.82 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24882 | LOW2.81 | gpg 2.4.7-21+deb13u1+b5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpgconf 2.4.7-21+deb13u1+b5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncurses6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | LOW2.7 | perl 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | 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-73088 | LOW2.7 | browserslist 4.28.4 fixed in 4.28.7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-73089 | LOW2.7 | browserslist 4.28.4 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-111756 | LOW2.7 | follow-redirects 1.16.0 fixed in 1.16.1 | 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-67213 | LOW2.7 | nanoid 3.3.8 fixed in 3.3.18, 5.1.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-67214 | LOW2.7 | nanoid 3.3.8 fixed in 3.3.16, 5.1.16 | 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-93749 | LOW2.7 | source-map-js 1.0.2 fixed in 1.2.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-93749 | LOW2.7 | source-map-js 1.2.1 fixed in 1.2.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-109869 | LOW2.7 | undici 6.28.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19534 | LOW2.7 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-109924 | LOW2.7 | undici 6.28.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% 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-2026-73086 | LOW2.66 | nanoid 3.3.8 fixed in 3.3.12, 5.1.11 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107817 | LOW2.64 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.64 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42307 | LOW2.64 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28420 | LOW2.64 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42307 | LOW2.64 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-86141 | LOW2.64 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-92386 | LOW2.58 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libgbm1 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-95209 | LOW2.5 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2026-95210 | LOW2.5 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45931 | LOW2.5 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6004 | LOW2.45 | libssh 0.9.6-16.el8_10 fixed in 0.10.6-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | LOW2.4 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW2.34 | git 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | LOW2.34 | git 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14017 | LOW2.34 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | LOW2.34 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW2.34 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW2.34 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW2.34 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-109828 | LOW2.34 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59846 | LOW2.34 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | LOW2.34 | openldap 2.4.46-21.el8_10 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW2.34 | openldap 2.4.46-21.el8_10 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13057 | LOW2.34 | openldap 2.4.46-21.el8_10 fixed in 2.4.48+dfsg-1 | 6.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-13565 | LOW2.34 | openldap 2.4.46-21.el8_10 fixed in 2.4.48+dfsg-1 | 5.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW2.34 | openldap 2.4.46-21.el8_10 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW2.34 | openldap 2.4.46-21.el8_10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | LOW2.34 | pcre2 10.32-3.el8_6 fixed in 10.42-1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-4677 | LOW2.34 | vim 2:9.1.1230-2+deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28419 | LOW2.34 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32249 | LOW2.34 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52859 | LOW2.34 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2008-4677 | LOW2.34 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28419 | LOW2.34 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32249 | LOW2.34 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52859 | LOW2.34 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4877 | LOW2.29 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | apt 3.0.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107929 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-112946 | LOW2.22 | vite 8.2.1 fixed in 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg 2.4.7-21+deb13u1+b5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgconf 2.4.7-21+deb13u1+b5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-111755 | LOW2.12 | follow-redirects 1.16.0 fixed in 1.16.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-104844 | LOW2.12 | postcss-selector-parser 7.1.4 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-85024 | LOW2.12 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-45913 | LOW2.12 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libgl1 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libglvnd0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45924 | LOW2.12 | libglx0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-29070 | LOW2.12 | liblcms2-2 2.16-2+deb13u2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-45913 | LOW2.12 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-45919 | LOW2.12 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-45922 | LOW2.12 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-53906 | LOW2.09 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-53906 | LOW2.09 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-18018 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW1.99 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | LOW1.99 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW1.99 | jq 1.7.1-6+deb13u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW1.99 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW1.99 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | LOW1.99 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | LOW1.99 | openldap 2.4.46-21.el8_10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-1000382 | LOW1.99 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-1000382 | LOW1.99 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW1.98 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89162 | LOW1.98 | pcre2 10.32-3.el8_6 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| 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-82209 | LOW1.86 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl3t64-gnutls 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW1.86 | libssh 0.9.6-16.el8_10 fixed in 0.11.5-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4878 | LOW1.84 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpg 2.4.7-21+deb13u1+b5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgconf 2.4.7-21+deb13u1+b5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg 2.4.7-21+deb13u1+b5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+deb13u1+b5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncurses6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | libmariadb3 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-client 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-client-core 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-common 1:11.8.6-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8277 | LOW1.58 | libssh 0.9.6-16.el8_10 fixed in 0.11.2-1+deb13u1 | 0.4% 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 |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.37-2+b10 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login.defs 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.14-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
| CVE-2026-18540 | LOW1.33 | undici 6.28.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.32 | vim 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28422 | LOW1.32 | vim-common 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| 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.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-73078 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73073 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-73076 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73077 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 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.2.1-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-73072 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2020-27748 | NONE0 | xdg-utils 1.2.1-2 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.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-73070 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.1.1230-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2008-4677 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2017-1000382 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-32249 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-runtime 2:9.1.1230-2+deb13u2 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.2.1-2 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.1.1230-2+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.