Last scanned:
··This base/runtime image is a reasonable foundation, but it ships vulnerabilities worth remediating in the images built on top of it. The most serious item, CVE-2026-6653 in libxml2, could let an application crash or hang when it parses untrusted XML, and several other libxml2 flaws such as CVE-2026-86138 could lead to memory corruption or code execution if an application parses hostile XML. Those risks are inherited only by images that actually process external XML with the PHP XML extensions, since this image runs an interactive PHP shell with no exposed ports and does not parse network input itself. Teams building on this image should confirm whether their applications handle untrusted XML and patch libxml2 in the final image where that is the case. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
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 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86139 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86140 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86142 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86144 | MEDIUM6.24 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM5.5 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM5.5 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM5.5 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6-dev 2.41-12+deb13u4 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 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libasan8 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libatomic1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libcc1-0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgcc-14-dev 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgomp1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libhwasan0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libitm1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | liblsan0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libquadmath0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libstdc++-14-dev 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libtsan2 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libubsan1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9545 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-2 2.1.28+dfsg1-9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM4.5 | libsasl2-modules-db 2.1.28+dfsg1-9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-9080 | MEDIUM4.38 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | MEDIUM4.38 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | cpp-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | cpp-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | g++-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | g++-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libasan8 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libatomic1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-dev-bin 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6-dev 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libcc1-0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgcc-14-dev 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgomp1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libhwasan0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libitm1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | liblsan0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libquadmath0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libstdc++-14-dev 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libtsan2 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libubsan1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libbinutils 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6-dev 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libctf0 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2020-15719 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | LOW3.9 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.9 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | LOW3.9 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | libsframe1 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | LOW3.9 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | LOW3.9 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-66864 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19548 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90802 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90830 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91779 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91780 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91782 | LOW3.9 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.9 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | LOW3.72 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | LOW3.31 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | LOW3.31 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-115207 | LOW3.3 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW3.3 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-91781 | LOW3.3 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW3.3 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | LOW3.24 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | LOW3.17 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | LOW3.12 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3389 | LOW3.04 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-42250 | LOW3 | bzip2 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-8458 | LOW2.92 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | LOW2.92 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.88 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.82 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-10536 | LOW2.82 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | LOW2.77 | cpp-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | cpp-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | g++-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | g++-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | gcc-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | gcc-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW2.7 | curl 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-12064 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86141 | LOW2.64 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW2.34 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils-common 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19548 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90802 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90830 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91779 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91780 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91782 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW2.34 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | LOW2.34 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW2.34 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW2.34 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW2.34 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2008-1687 | LOW2.34 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.34 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW2.34 | patch 2.8-2 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | LOW2.34 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.34 | patch 2.8-2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-56288 | LOW2.34 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.34 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW2.34 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107929 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 8.14.1-2+deb13u7 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-32256 | LOW1.99 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW1.99 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-18018 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW1.99 | patch 2.8-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.98 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-91781 | LOW1.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.86 | curl 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl4t64 8.14.1-2+deb13u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.37-2+b10 No fix yet | — | Post-Exploit |
| CVE-2026-95209 | LOW1.5 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95210 | LOW1.5 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| TEMP-0628843-DBAD28 | LOW1.5 | login.defs 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.14-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98084 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89632 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74520 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68393 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72500 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74513 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90240 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90317 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93148 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98047 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98048 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98296 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98599 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93144 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90211 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90256 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100074 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23143 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68295 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68421 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72355 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72365 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72367 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72388 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-74354 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74529 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74542 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80614 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80655 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89639 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90040 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90142 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90177 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90217 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90231 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90324 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90351 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90363 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90367 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90408 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90409 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90422 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92518 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93044 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93135 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93270 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93276 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97526 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97538 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97960 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97962 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98049 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98053 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98062 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98115 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98118 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98119 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98134 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98228 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98277 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98376 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98408 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98674 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68375 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72366 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72497 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74728 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80705 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89812 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90144 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90261 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90306 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90424 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93181 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93230 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97928 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98038 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98147 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98431 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90086 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98032 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89826 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89866 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89935 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-89534 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90260 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90427 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98444 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98747 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98813 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98843 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98875 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98616 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98878 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98883 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98894 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98897 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98914 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98916 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98917 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98924 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98926 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98929 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98932 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98942 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98946 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98951 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98954 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98958 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98966 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98972 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98974 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98975 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98977 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98978 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98981 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98983 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98985 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98989 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98993 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98996 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98999 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99002 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99009 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99014 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99019 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99021 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99026 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99027 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99028 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99041 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99044 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99076 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99077 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99082 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99083 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99085 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99086 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99087 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99092 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-99098 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 4.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2018-21232 | NONE0 | re2c 4.1-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2903 | NONE0 | re2c 4.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | — | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98874 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.113-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.