Last scanned:
··This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The most significant items are libxml2 flaws such as CVE-2026-6653, which mainly risk service crashes, and CVE-2026-86138, which could corrupt memory if untrusted XML is parsed. Their impact depends on whether the Airflow deployment or one of its providers or plugins actually parses XML from external sources, which is not normal for Airflow. Updating the libxml2 package is the straightforward way to address these findings.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH7.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-2g87-pp6c-29x5 | MEDIUM6.96 | aiohttp 3.14.3 fixed in 3.14.4 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-74860 | MEDIUM6.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 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+dhi3 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+dhi3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | gcc-14-base 14.2.0-19+deb13u0+dhi6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libgcc-s1 14.2.0-19+deb13u0+dhi6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libstdc++6 14.2.0-19+deb13u0+dhi6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| GHSA-6v7p-g79w-8964 | MEDIUM6 | msgpack 1.1.2 fixed in 1.2.1 | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-49261 | MEDIUM5.88 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49261 | MEDIUM5.88 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49261 | MEDIUM5.88 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-49261 | MEDIUM5.88 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | gcc-14-base 14.2.0-19+deb13u0+dhi6 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libgcc-s1 14.2.0-19+deb13u0+dhi6 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libstdc++6 14.2.0-19+deb13u0+dhi6 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM5.5 | libsqlite3-0 3.46.1-7+deb13u2+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM5.5 | libsqlite3-0 3.46.1-7+deb13u2+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM5.5 | zlib1g 1:1.3.dfsg+really1.3.1-1+deb13u0+dhi4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44172 | MEDIUM5.46 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58055 | MEDIUM5.4 | libnghttp2-14 1.64.0-1.1+deb13u1+dhi3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85746 | MEDIUM5.28 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-92262 | MEDIUM5.28 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97380 | MEDIUM5.28 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-111748 | MEDIUM5.2 | aiohttp 3.14.3 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3389 | MEDIUM5.07 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107818 | MEDIUM5.04 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6+deb13u0+dhi2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib1g 1:1.3.dfsg+really1.3.1-1+deb13u0+dhi4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM4.88 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-97687 | MEDIUM4.86 | urllib3 2.7.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44168 | MEDIUM4.8 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | MEDIUM4.72 | libexpat1 2.9.0-1~deb13u1+dhi1 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-113351 | MEDIUM4.72 | libexpat1-dev 2.9.0-1~deb13u1+dhi1 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | liblastlog2-2 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | liblastlog2-2 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.68 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM4.68 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-106583 | MEDIUM4.68 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | util-linux 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1.2+deb13u3+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-86047 | MEDIUM4.62 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12064 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8932 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | libperl5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg1-9+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules 2.1.28+dfsg1-9+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg1-9+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107815 | MEDIUM4.5 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106553 | MEDIUM4.5 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106555 | MEDIUM4.5 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-59999 | MEDIUM4.5 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60000 | MEDIUM4.5 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-89407 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-core 2.18.8 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-89425 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-core 2.18.8 fixed in 2.21.7, 2.22.3, 2.18.11 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-68497 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-91776 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.18.11, 2.21.7, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-91777 | MEDIUM4.5 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.21.7, 2.18.11, 2.22.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-111064 | MEDIUM4.5 | aiohttp 3.14.3 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-111066 | MEDIUM4.5 | aiohttp 3.14.3 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-97689 | MEDIUM4.5 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.4 | libexpat1 2.9.0-1~deb13u1+dhi1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-66382 | MEDIUM4.4 | libexpat1-dev 2.9.0-1~deb13u1+dhi1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-9080 | MEDIUM4.38 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.38 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107823 | MEDIUM4.32 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM4.32 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM4.32 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.2-2+deb13u0+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-111065 | MEDIUM4.24 | aiohttp 3.14.3 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.41-12+deb13u4+dhi1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | liblastlog2-2 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107821 | MEDIUM4.02 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-60585 | LOW3.96 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | krb5-user 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssrpc4t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkadm5clnt-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkadm5srv-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkdb5-10t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.21.3-5+deb13u1+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106552 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-106585 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59998 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60001 | LOW3.9 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58469 | LOW3.9 | wget 1.25.0-2+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59889 | LOW3.9 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.21.5, 2.18.9, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| GHSA-mhm7-754m-9p8w | LOW3.9 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.18.9, 2.21.5 | — | Directly Exposed |
| CVE-2026-84377 | LOW3.9 | litellm 1.85.7 fixed in 1.88.6, 1.89.7, 1.90.7, 1.91.5, 1.92.2, 1.93.2, 1.94.3, 1.95.1, 1.96.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13346 | LOW3.9 | pip 26.0.1 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | LOW3.9 | libgcrypt20 1.11.0-7+deb13u1+dhi1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW3.9 | libgcrypt20 1.11.0-7+deb13u1+dhi1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.9 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | LOW3.9 | libldap2 2.6.10+dfsg-1+dhi1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW3.9 | libldap2 2.6.10+dfsg-1+dhi1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW3.9 | libldap2 2.6.10+dfsg-1+dhi1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW3.9 | libldap2 2.6.10+dfsg-1+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.9 | libsqlite3-0 3.46.1-7+deb13u2+dhi3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | LOW3.9 | libxslt1.1 1.1.35-1.2+deb13u3+dhi2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107822 | LOW3.84 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-60331 | LOW3.84 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-111750 | LOW3.84 | aiohttp 3.14.3 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.2-2+deb13u0+dhi2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.5.2-3+deb13u0+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.25.5-3+deb13u0+dhi1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | LOW3.72 | libp11-kit0 0.25.5-3+deb13u0+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60747 | LOW3.72 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-59890 | LOW3.66 | setuptools 70.3.0 fixed in 83.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | LOW3.66 | setuptools 82.0.1 fixed in 83.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | LOW3.54 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6791 | LOW3.54 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77117 | LOW3.54 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80489 | LOW3.54 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.54 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6791 | LOW3.54 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-77117 | LOW3.54 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80489 | LOW3.54 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15146 | LOW3.54 | wget 1.25.0-2+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49844 | LOW3.54 | org.apache.logging.log4j:log4j-api 2.25.4 fixed in 2.25.5, 2.26.1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-49261 | LOW3.53 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-49261 | LOW3.53 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-49261 | LOW3.53 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW3.48 | pip 26.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW3.42 | libperl5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl 5.40.1-6+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.40.1-6+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-modules-5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60002 | LOW3.38 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-73282 | LOW3.36 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-83557 | LOW3.36 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-111749 | LOW3.36 | aiohttp 3.14.3 fixed in 3.14.4 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2017-14159 | LOW3.31 | libldap2 2.6.10+dfsg-1+dhi1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | LOW3.31 | libodbc2 2.3.12-2+deb13u1+dhi0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | LOW3.31 | libodbcinst2 2.3.12-2+deb13u1+dhi0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | LOW3.31 | odbcinst 2.3.12-2+deb13u1+dhi0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | LOW3.31 | unixodbc-common 2.3.12-2+deb13u1+dhi0 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | LOW3.3 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6368 | LOW3.3 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50812 | LOW3.3 | sqlite3 3.46.1-7+deb13u2+dhi3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50813 | LOW3.3 | sqlite3 3.46.1-7+deb13u2+dhi3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW3.3 | tar 1.35+dfsg-3.1+deb13u0+dhi3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW3.3 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+deb13u0+dhi4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW3.3 | pip 26.0.1 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW3.3 | libsqlite3-0 3.46.1-7+deb13u2+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107816 | LOW3.24 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85985 | LOW3.24 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59995 | LOW3.24 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59996 | LOW3.24 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59997 | LOW3.24 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-73283 | LOW3.24 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-115506 | LOW3.2 | libexpat1 2.9.0-1~deb13u1+dhi1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-115506 | LOW3.2 | libexpat1-dev 2.9.0-1~deb13u1+dhi1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86409 | LOW3.18 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | LOW3.18 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8674 | LOW3.18 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | liblastlog2-2 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | LOW3.18 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58470 | LOW3.18 | wget 1.25.0-2+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19032 | LOW3.18 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.18.10, 2.21.6, 2.22.2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54515 | LOW3.18 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 3.1.4, 2.18.9, 2.21.5, 2.22.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-77310 | LOW3.18 | com.fasterxml.jackson.core:jackson-databind 2.18.8 fixed in 2.18.9, 2.21.5, 2.22.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97688 | LOW3.18 | urllib3 2.7.0 fixed in 2.8.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-47273 | LOW3.17 | setuptools 70.3.0 fixed in 78.1.1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11979 | LOW3.12 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-85091 | LOW3 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+deb13u0+dhi4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW3 | pip 26.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-111063 | LOW2.96 | aiohttp 3.14.3 fixed in 3.14.4 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-107708 | LOW2.94 | krb5-user 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | LOW2.94 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18374 | LOW2.94 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libgssrpc4t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkadm5clnt-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkadm5srv-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkdb5-10t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.21.3-5+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47023 | LOW2.94 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | LOW2.92 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.88 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.7.0-5+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.7.0-5+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.7.0-5+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.7.0-5+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | liblastlog2-2 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.41.5-0+deb13u1+dhi3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.82 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | dirmngr 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gnupg2 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpg-agent 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgconf 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgsm 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-24882 | LOW2.81 | dirmngr 2.4.7-21+deb13u1+dhi4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gnupg2 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpg 2.4.7-21+deb13u1+dhi4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpg-agent 2.4.7-21+deb13u1+dhi4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpgconf 2.4.7-21+deb13u1+dhi4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpgsm 2.4.7-21+deb13u1+dhi4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24882 | LOW2.81 | gpgv 2.4.7-21+deb13u1+dhi4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncurses6 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-96512 | LOW2.81 | sudo 1.9.16p2-3+deb13u2+dhi3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | LOW2.7 | perl 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-base 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-107161 | LOW2.7 | sasl2-bin 2.1.28+dfsg1-9+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-6110 | LOW2.69 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 24.9% High Exploitation Risk | Directly Exposed |
| CVE-2020-15778 | LOW2.69 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 13.7% High Exploitation Risk | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107817 | LOW2.64 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-60184 | LOW2.64 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3.1+deb13u0+dhi3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3.1+deb13u0+dhi3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86141 | LOW2.64 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3+dhi3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1.2+deb13u3+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW2.58 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-85745 | LOW2.58 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-106586 | LOW2.58 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-58471 | LOW2.56 | wget 1.25.0-2+dhi2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58472 | LOW2.56 | wget 1.25.0-2+dhi2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW2.52 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89092 | LOW2.52 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW2.52 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89092 | LOW2.52 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95209 | LOW2.5 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | — | Directly Exposed |
| CVE-2026-95210 | LOW2.5 | libgnutls30t64 3.8.9-3+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18739 | LOW2.5 | libpopt0 1.19+dfsg-2+deb13u0+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18743 | LOW2.5 | libpopt0 1.19+dfsg-2+deb13u0+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | LOW2.45 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19499 | LOW2.45 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW2.4 | libperl5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl 5.40.1-6+deb13u1+dhi3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.40.1-6+deb13u1+dhi3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-modules-5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW2.34 | coreutils 9.7-3+dhi4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.7-3+dhi4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.34 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-12+deb13u0+dhi2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-12+deb13u0+dhi2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.10-4+deb13u0+dhi2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW2.34 | git 1:2.47.3-0+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | LOW2.34 | git 1:2.47.3-0+deb13u1+dhi2 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47268 | LOW2.34 | iputils-ping 3:20240905-3+deb13u0+dhi2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.34 | krb5-user 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | krb5-user 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | krb5-user 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | LOW2.34 | ldap-utils 2.6.10+dfsg-1+dhi1 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW2.34 | ldap-utils 2.6.10+dfsg-1+dhi1 No fix yet | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2020-15719 | LOW2.34 | ldap-utils 2.6.10+dfsg-1+dhi1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-22185 | LOW2.34 | ldap-utils 2.6.10+dfsg-1+dhi1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010024 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.34 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4756 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010024 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.34 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14017 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssrpc4t64 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssrpc4t64 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssrpc4t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkadm5clnt-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkadm5clnt-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkadm5clnt-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkadm5srv-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkadm5srv-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkadm5srv-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkdb5-10t64 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkdb5-10t64 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkdb5-10t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.21.3-5+deb13u1+dhi2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.21.3-5+deb13u1+dhi2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.21.3-5+deb13u1+dhi2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-2243 | LOW2.34 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2007-2768 | LOW2.34 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3234 | LOW2.34 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2016-20012 | LOW2.34 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15919 | LOW2.34 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 3.5% Low-Moderate Risk | Directly Exposed |
| CVE-2020-14145 | LOW2.34 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | LOW2.34 | sqlite3 3.46.1-7+deb13u2+dhi3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-82474 | LOW2.34 | sudo 1.9.16p2-3+deb13u2+dhi3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.35+dfsg-3.1+deb13u0+dhi3 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-16599 | LOW2.34 | wget 1.25.0-2+dhi2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | apt 3.0.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.4+dhi0 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt-transport-https 3.0.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt-utils 3.0.4+dhi0 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107929 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | libapt-pkg7.0 3.0.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | libapt-pkg7.0 3.0.4+dhi0 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-97399 | LOW2.22 | libc-dev-bin 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-97399 | LOW2.22 | libc6-dev 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107929 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-106582 | LOW2.22 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55654 | LOW2.22 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18839 | LOW2.2 | libpopt0 1.19+dfsg-2+deb13u0+dhi1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | dirmngr 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gnupg2 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpg-agent 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgconf 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgsm 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-105712 | LOW2.16 | gpgv 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-73281 | LOW2.1 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-18018 | LOW1.99 | coreutils 9.7-3+dhi4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.7-3+dhi4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW1.99 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | LOW1.99 | git 1:2.47.3-0+deb13u1+dhi2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-26458 | LOW1.99 | krb5-user 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | LOW1.99 | ldap-utils 2.6.10+dfsg-1+dhi1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW1.99 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssrpc4t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkadm5clnt-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkadm5srv-mit12 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkdb5-10t64 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.21.3-5+deb13u1+dhi2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | liblastlog2-2 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login.defs 1:4.17.4-2+dhi1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.17.4-2+dhi1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-1013 | LOW1.99 | unixodbc 2.3.12-2+deb13u1+dhi0 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.41.5-0+deb13u1+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-106584 | LOW1.98 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-106587 | LOW1.98 | openssh-client 1:10.0p1-7+deb13u4+dhi2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW1.98 | sqlite3 3.46.1-7+deb13u2+dhi3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.86 | curl 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl4t64 8.14.1-2+deb13u7+dhi1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login.defs 1:4.17.4-2+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2+dhi1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | dirmngr 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gnupg2 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpg 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpg-agent 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgconf 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgsm 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-57062 | LOW1.74 | gpgv 2.4.7-21+deb13u1+dhi4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.4.7-21+deb13u1+dhi4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gnupg2 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg 2.4.7-21+deb13u1+dhi4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.4.7-21+deb13u1+dhi4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.4.7-21+deb13u1+dhi4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.4.7-21+deb13u1+dhi4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3219 | LOW1.68 | gpgv 2.4.7-21+deb13u1+dhi4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncurses6 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libncursesw6 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | libperl5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2+deb13u0+dhi5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6+deb13u1+dhi3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | libmariadb3 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | libmariadb3-compat 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-client 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-client-compat 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-client-core 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mariadb-common 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-61081 | LOW1.62 | mysql-common 1:11.8.9+maria~deb13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.37-2+dhi1 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login.defs 1:4.17.4-2+dhi1 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.17.4-2+dhi1 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.35+dfsg-3.1+deb13u0+dhi3 No fix yet | — | Post-Exploit |
| CVE-2005-1119 | LOW1.07 | sudo 1.9.16p2-3+deb13u2+dhi3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 70.3.0 fixed in 84.1.0 | — | Directly Exposed |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 82.0.1 fixed in 84.1.0 | — | Directly Exposed |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-24882 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98084 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74520 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68393 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72500 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74513 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90240 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90317 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93148 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98047 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98048 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98296 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98599 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93144 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90211 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90256 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100074 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23143 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68295 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68421 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72355 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72365 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72367 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72388 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74354 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74529 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74542 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80614 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80655 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | — | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89639 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90040 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90142 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90177 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90217 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90231 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90324 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90351 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90363 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90367 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90408 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90409 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90422 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92518 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93044 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93135 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93270 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93276 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97526 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97538 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97960 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97962 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98049 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98053 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98062 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98115 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98118 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98119 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98134 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98228 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98277 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98376 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98408 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98674 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68375 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72366 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72497 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74728 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80705 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89812 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90144 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90261 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90306 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90424 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93181 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93230 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97928 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98038 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98147 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98431 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90086 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98032 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89826 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89866 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89935 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89534 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90260 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90427 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98444 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98747 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98813 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98843 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98875 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98616 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98878 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98883 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98894 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98897 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98914 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98916 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98917 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98924 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98926 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98929 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98932 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98942 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98946 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98951 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98954 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98958 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98966 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98972 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98974 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98975 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98977 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98978 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98981 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98983 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98985 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98989 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98993 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98996 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98999 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99002 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99009 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99014 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99019 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99021 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99026 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99027 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99028 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99041 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99044 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99076 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99077 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99082 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99083 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99085 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99086 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99087 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99092 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99098 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 32.4% High Exploitation Risk | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-97399 | NONE0 | libc-l10n 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | locales 2.41-12+deb13u4+dhi1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-105712 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gnupg-l10n 2.4.7-21+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | — | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98874 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.115-2+dhi0 No fix yet | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.