Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit heap buffer overflows in Perl and OpenSSL (CVE-2026-8376, CVE-2026-31789) to execute arbitrary code or crash the service, potentially leading to host compromise. Note that CVE-2026-31789 only affects 32-bit platforms, so 64-bit deployments are not subject to that specific flaw, but other high-severity issues remain. The image contains 3390 exposed vulnerabilities, including 85 rated 7.0 or higher, making remediation mandatory before any production use.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-8376 | HIGH8.33 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | HIGH8.33 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-4609 | HIGH8.16 | linux-libc-dev 6.12.74-2 No fix yet | 32.1% High Exploitation Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | HIGH7.84 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.12.74-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19449 | HIGH7.8 | linux-libc-dev 6.12.74-2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 6.12.74-2 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46333 | HIGH7.8 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 6.12.74-2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 6.12.74-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | HIGH7.73 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3039 | HIGH7.5 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5946 | HIGH7.5 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5121 | HIGH7.5 | libarchive13t64 3.7.4-4 fixed in 3.7.4-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.11.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5201 | HIGH7.5 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4 fixed in 2.42.12+dfsg-4+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16226 | HIGH7.5 | liblmdb0 0.9.31-1+b2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16228 | HIGH7.5 | liblmdb0 0.9.31-1+b2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3+deb13u1 No fix yet | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.12.74-2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.12.74-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28388 | HIGH7.5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28389 | HIGH7.5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28390 | HIGH7.5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6637 | HIGH7.48 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6638 | HIGH7.48 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6637 | HIGH7.48 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6638 | HIGH7.48 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43037 | HIGH7.48 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6637 | HIGH7.48 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6638 | HIGH7.48 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13321 | HIGH7.31 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH7.14 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6477 | HIGH7.14 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6477 | HIGH7.14 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-10263 | HIGH7.14 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63797 | HIGH7.14 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6477 | HIGH7.14 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | HIGH7.1 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46242 | HIGH7 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6478 | MEDIUM6.97 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6478 | MEDIUM6.97 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6478 | MEDIUM6.97 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM6.88 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM6.88 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-43133 | MEDIUM6.71 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-25724 | MEDIUM6.63 | libarchive13t64 3.7.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libdebuginfod-common 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libdebuginfod-common 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libdebuginfod1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libdebuginfod1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libdw1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libdw1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd-dev 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd-shared 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u1 fixed in 4.7.0-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22069 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38627 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23231 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23281 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23354 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23387 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23412 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23413 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23422 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23427 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23428 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31474 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31506 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31530 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31566 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31582 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31730 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31731 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31787 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43007 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43059 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43120 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43128 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43138 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43150 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43178 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43205 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43260 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43378 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45837 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45853 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45866 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45867 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45879 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45882 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45885 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45891 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45902 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45914 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45916 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45936 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45938 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45946 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45989 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45998 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46001 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46084 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46121 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46162 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46246 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53097 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53098 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53119 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53233 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53234 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53366 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63794 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63804 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64600 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1+b2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.12.74-2 No fix yet | 80.3% Actively Exploited | Directly Exposed |
| CVE-2026-11331 | MEDIUM6.38 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11605 | MEDIUM6.38 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11622 | MEDIUM6.38 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11721 | MEDIUM6.38 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12617 | MEDIUM6.38 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13204 | MEDIUM6.38 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4111 | MEDIUM6.38 | libarchive13t64 3.7.4-4 fixed in 3.7.4-4+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4424 | MEDIUM6.38 | libarchive13t64 3.7.4-4 fixed in 3.7.4-4+deb13u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-14164 | MEDIUM6.38 | libarchive13t64 3.7.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM6.38 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdebuginfod-common 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdebuginfod1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdw1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.11.0-7 fixed in 1.11.0-7+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32316 | MEDIUM6.38 | libjq1 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40164 | MEDIUM6.38 | libjq1 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | liblcms2-2 2.16-2 fixed in 2.16-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.64.0-1.1 fixed in 1.64.0-1.1+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libngtcp2-16 1.11.0-1 fixed in 1.11.0-1+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40170 | MEDIUM6.38 | libngtcp2-crypto-gnutls8 1.11.0-1 fixed in 1.11.0-1+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6479 | MEDIUM6.38 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6479 | MEDIUM6.38 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31669 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43186 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6479 | MEDIUM6.38 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u1 fixed in 4.7.0-3+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43074 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6476 | MEDIUM6.12 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6476 | MEDIUM6.12 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6476 | MEDIUM6.12 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23244 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23325 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23363 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31430 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31614 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43380 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45851 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46094 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46140 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46293 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53346 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31786 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43056 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43330 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46155 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap-dev 1:2.75-10+b8 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.75-10+b8 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45898 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45972 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46145 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46152 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46166 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46176 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46316 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52951 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52976 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53202 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53203 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53277 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53360 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53398 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53399 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63795 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63824 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63829 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63830 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63831 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63875 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63884 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63886 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63887 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63888 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63899 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63917 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63921 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63922 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63924 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63939 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63952 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63956 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63962 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63970 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63993 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63994 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64007 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64009 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64017 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64018 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64026 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64051 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64061 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64099 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64113 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64132 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64137 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64191 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64217 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64265 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64268 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64271 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64276 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64277 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64287 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64296 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64303 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64304 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64364 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64375 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64378 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64382 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64383 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64385 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64387 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64434 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64483 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64490 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64534 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64552 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64556 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64558 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31772 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43023 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43304 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43332 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43341 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45861 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45910 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46076 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46114 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46251 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52933 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53031 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53110 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53182 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53192 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53193 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53209 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53235 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53260 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53341 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53381 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53384 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53388 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53391 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53392 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53397 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63800 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63801 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63802 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63807 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63808 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63809 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63823 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63826 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63883 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63889 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63891 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63894 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63896 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63898 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63901 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63912 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63913 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63914 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63916 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63918 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63919 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63920 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63925 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63928 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63938 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63940 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63941 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63944 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63945 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63946 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63947 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63957 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63958 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63971 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63975 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63978 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63979 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63984 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63987 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63992 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63996 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64000 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64001 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64002 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64011 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64015 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64024 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64025 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64029 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64032 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64034 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64047 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64048 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64053 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64068 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64098 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64102 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64109 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64111 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64114 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64115 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64117 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64119 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64136 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64160 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64174 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64189 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64192 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64216 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64247 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64251 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64255 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64266 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64280 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64283 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64286 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64298 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64305 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64306 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64312 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64317 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64319 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64320 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64321 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64322 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64323 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64324 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64340 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64341 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64342 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64354 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64355 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64372 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64377 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64379 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64380 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64384 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64401 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64402 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64414 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64418 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64422 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64448 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64456 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64470 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64471 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64473 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64475 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64481 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64508 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64515 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64520 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64523 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64525 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64527 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64530 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64531 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64539 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64543 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64548 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64551 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64554 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64557 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64559 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64560 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5947 | MEDIUM5.9 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.11.0-7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.74-2 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.12.74-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-10723 | MEDIUM5.78 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | liblmdb0 0.9.31-1+b2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.78 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM5.7 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6475 | MEDIUM5.7 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6475 | MEDIUM5.7 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd-dev 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd-shared 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53094 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6475 | MEDIUM5.7 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5918 | MEDIUM5.61 | libarchive13t64 3.7.4-4 fixed in 3.7.4-4+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | MEDIUM5.61 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-10822 | MEDIUM5.52 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4426 | MEDIUM5.52 | libarchive13t64 3.7.4-4 fixed in 3.7.4-4+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | MEDIUM5.52 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-39979 | MEDIUM5.52 | libjq1 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31470 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64535 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd-dev 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd-dev 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd-shared 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd-shared 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31525 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53081 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53085 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53092 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27447 | MEDIUM5.35 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31504 | MEDIUM5.35 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39314 | MEDIUM5.27 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | MEDIUM5.27 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40147 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39956 | MEDIUM5.18 | libjq1 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31511 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43044 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23246 | MEDIUM5.02 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.12.74-2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52908 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.12.74-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-60753 | MEDIUM4.67 | libarchive13t64 3.7.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5745 | MEDIUM4.67 | libarchive13t64 3.7.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | MEDIUM4.67 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libdebuginfod-common 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libdebuginfod-common 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libdebuginfod1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libdebuginfod1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libdw1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libdw1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33947 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41256 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41257 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43894 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43896 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44777 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47770 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54679 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40612 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-14027 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21709 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22116 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22117 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71239 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71265 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71266 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71267 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71286 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71288 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71291 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71294 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71295 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71300 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71311 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71314 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22981 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22985 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22993 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23070 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23104 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23249 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23250 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23251 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23252 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23284 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23285 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23297 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23308 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23316 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23324 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23334 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23347 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23360 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23369 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23373 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23375 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23380 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23386 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23417 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23426 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23438 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23445 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23461 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23464 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23466 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23470 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31394 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31406 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31429 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31434 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31435 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31436 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31438 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31439 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31440 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31467 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31479 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31480 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31482 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31483 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31492 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31499 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31520 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31522 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31528 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31533 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31542 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31549 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31551 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31554 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31556 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31559 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31561 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31562 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31565 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31575 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31593 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31604 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31638 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31639 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31645 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31646 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31647 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31666 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31689 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31693 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31714 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31732 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31733 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31736 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31739 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31740 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31741 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31756 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31765 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31774 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31779 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43012 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43013 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43017 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43018 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43019 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43033 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43054 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43057 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43063 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43065 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43077 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43081 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43082 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43086 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43090 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43092 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43108 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43109 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43145 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43148 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43157 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43169 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43175 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43177 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43189 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43199 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43200 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43201 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43210 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43214 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43220 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43221 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43229 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43238 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43240 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43243 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43252 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43265 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43272 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43278 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43292 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43293 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43297 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43300 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43306 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43312 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43315 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43319 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43320 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43325 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43326 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43331 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43333 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43337 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43345 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43346 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43354 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43360 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43365 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43366 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43372 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43374 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43392 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43393 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43394 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43395 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43397 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43403 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43405 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43406 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43408 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43412 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43436 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43441 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43444 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43455 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43457 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43467 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43468 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43469 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43470 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43471 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43473 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43480 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43482 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43485 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43486 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43487 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43488 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45847 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45848 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45849 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45863 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45864 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45865 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45869 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45872 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45874 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45875 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45880 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45881 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45883 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45884 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45886 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45888 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45890 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45895 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45900 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45911 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45913 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45921 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45922 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45924 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45925 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45928 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45947 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45950 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45962 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45969 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45973 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45976 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45982 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46007 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46016 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46034 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46041 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46048 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46061 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46063 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46072 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46073 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46074 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46089 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46096 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46106 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46109 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46115 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46126 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46131 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46138 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46139 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46142 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46143 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46144 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46165 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46188 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46207 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46211 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46216 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46255 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46256 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46260 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46261 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46262 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46276 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46282 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46283 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46286 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46287 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46296 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46329 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52904 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52928 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52941 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52964 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52967 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52980 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52996 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53013 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53014 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53032 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53038 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53051 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53052 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53058 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53084 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53101 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53105 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53123 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53126 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53140 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53142 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53144 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53151 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53152 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53154 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53180 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53183 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53184 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53190 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53191 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53205 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53210 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53214 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53241 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53251 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53261 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53271 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53274 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53279 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53288 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53293 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53298 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53318 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53321 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53328 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53331 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53336 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53343 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53347 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53350 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53365 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53376 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53377 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53379 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53382 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53385 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53393 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53394 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53400 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53402 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53403 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63798 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63803 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63822 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63832 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63838 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63842 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63850 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63852 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63858 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63860 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63865 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63867 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63868 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63870 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63890 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63892 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63893 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63897 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63900 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63902 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63903 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63904 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63906 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63926 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63927 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63937 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63942 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63943 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63948 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63961 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63963 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63968 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63969 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63976 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63980 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63983 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63985 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63995 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64004 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64005 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64006 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64012 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64014 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64036 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64038 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64046 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64052 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64058 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64059 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64063 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64064 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64065 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64067 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64073 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64076 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64077 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64079 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64103 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64106 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64112 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64116 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64118 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64121 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64123 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64125 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-64126 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64127 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64128 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64133 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64157 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64159 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64170 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64173 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64177 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64178 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64185 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64190 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64205 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64206 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64210 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64212 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64220 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64222 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64223 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64225 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64235 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64239 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64243 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64245 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64253 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64279 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64284 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64290 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64299 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64307 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64308 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64309 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64310 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64315 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64316 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64326 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64327 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64328 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64329 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64330 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64333 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64336 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64338 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64343 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64344 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64346 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64347 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64351 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64357 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64360 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64362 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64363 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64365 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64368 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64369 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64373 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64374 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64381 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64403 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64404 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64405 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64406 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64407 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64408 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64409 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64411 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64412 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64413 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64416 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64423 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64424 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64433 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64436 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64452 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64454 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64455 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64458 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64463 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64472 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64477 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64478 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64479 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64487 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64496 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64507 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64510 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64517 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64524 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64529 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64540 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64541 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64542 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64545 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64546 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64547 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64553 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64555 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45933 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46201 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46327 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52974 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53369 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63810 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63821 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63843 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63844 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63845 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63851 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63853 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63869 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63871 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63872 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63876 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63877 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63929 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63964 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63973 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63974 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63990 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63991 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63997 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63998 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63999 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64003 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64039 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64060 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64062 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64066 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64070 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64078 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64105 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64131 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64134 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64144 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64146 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64153 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64155 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64158 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64163 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64179 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64180 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64182 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64183 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64184 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64187 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64213 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64214 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64227 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64231 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64232 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64237 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64244 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64254 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64256 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64275 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64294 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64297 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64301 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64332 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64334 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64335 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64352 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64370 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64376 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64388 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64415 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64417 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64419 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64428 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64430 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64435 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64465 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64474 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64476 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64480 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64482 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64486 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64488 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64489 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64511 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64512 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64513 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64514 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64519 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64537 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64544 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | MEDIUM4.64 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | MEDIUM4.64 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41079 | MEDIUM4.59 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.64.0-1.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6472 | MEDIUM4.59 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6472 | MEDIUM4.59 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6472 | MEDIUM4.59 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3039 | MEDIUM4.5 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5946 | MEDIUM4.5 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3039 | MEDIUM4.5 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5946 | MEDIUM4.5 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2014-8501 | MEDIUM4.5 | gdb 16.3-1 No fix yet | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15173 | MEDIUM4.5 | nmap 7.95+dfsg-3 No fix yet | 6.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28388 | MEDIUM4.5 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28389 | MEDIUM4.5 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | MEDIUM4.5 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | MEDIUM4.5 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3592 | MEDIUM4.5 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5950 | MEDIUM4.5 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-30571 | MEDIUM4.5 | libarchive13t64 3.7.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | MEDIUM4.5 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 10.2.0-1+b1 fixed in 10.2.0-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33948 | MEDIUM4.5 | libjq1 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd-dev 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd-dev 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd-dev 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd-shared 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd-shared 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd-shared 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64538 | MEDIUM4.5 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6637 | MEDIUM4.49 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6638 | MEDIUM4.49 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34990 | MEDIUM4.42 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13321 | MEDIUM4.39 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13321 | MEDIUM4.39 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6477 | MEDIUM4.28 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6478 | MEDIUM4.18 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdebuginfod-common 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdebuginfod1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdw1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22986 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23210 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23440 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23441 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23469 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31456 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43415 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46194 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-49809 | LOW3.98 | mtr 0.95-1.1+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55693 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55895 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57455 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57456 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59856 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59858 | LOW3.98 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.74-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47268 | LOW3.9 | iputils-arping 3:20240905-3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47268 | LOW3.9 | iputils-clockdiff 3:20240905-3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47268 | LOW3.9 | iputils-ping 3:20240905-3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-47268 | LOW3.9 | iputils-tracepath 3:20240905-3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15661 | LOW3.9 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11331 | LOW3.82 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11605 | LOW3.82 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11622 | LOW3.82 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11721 | LOW3.82 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12617 | LOW3.82 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13204 | LOW3.82 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11331 | LOW3.82 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11605 | LOW3.82 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11622 | LOW3.82 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11721 | LOW3.82 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12617 | LOW3.82 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13204 | LOW3.82 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-32316 | LOW3.82 | jq 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40164 | LOW3.82 | jq 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6479 | LOW3.82 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.13 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.13 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.13-minimal 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.13-minimal 3.13.5-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-25061 | LOW3.82 | tcpflow 1.6.1-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW3.74 | libjq1 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16t64 1.6.48-1+deb13u4 fixed in 1.6.48-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31401 | LOW3.74 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | vim 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6476 | LOW3.67 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-31431 | LOW3.65 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 94.5% Actively Exploited | Post-Exploit |
| CVE-2026-43284 | LOW3.65 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 93.2% Actively Exploited | Post-Exploit |
| CVE-2026-43500 | LOW3.65 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 92.9% Actively Exploited | Post-Exploit |
| CVE-2026-6474 | LOW3.65 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6474 | LOW3.65 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6474 | LOW3.65 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4878 | LOW3.57 | libcap2-bin 1:2.75-10+b8 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5947 | LOW3.54 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5947 | LOW3.54 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31790 | LOW3.54 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3593 | LOW3.53 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3593 | LOW3.53 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3593 | LOW3.53 | bind9-libs 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16224 | LOW3.53 | liblmdb0 0.9.31-1+b2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16225 | LOW3.53 | liblmdb0 0.9.31-1+b2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16227 | LOW3.53 | liblmdb0 0.9.31-1+b2 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-10723 | LOW3.47 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10723 | LOW3.47 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6475 | LOW3.42 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libdebuginfod-common 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libdebuginfod1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libdw1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | LOW3.37 | jq 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10822 | LOW3.31 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10822 | LOW3.31 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.26-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-39979 | LOW3.31 | jq 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1t64 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW3.31 | libssh2-1t64 1.11.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-14461 | LOW3.31 | mtr 0.95-1.1+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58058 | LOW3.31 | nmap 7.95+dfsg-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2673 | LOW3.31 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.13-minimal 3.13.5-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15028 | LOW3.31 | libarchive13t64 3.7.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-6293 | LOW3.3 | flex 2.6.4-8.2+b4 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-19519 | LOW3.3 | tcpdump 4.99.5-2 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-2 fixed in 4.9-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2014-8166 | LOW3.17 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6473 | LOW3.17 | libpq-dev 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6473 | LOW3.17 | libpq5 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6473 | LOW3.17 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6473 | LOW3.17 | postgresql-server-dev-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libclang-common-19-dev 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libclang-cpp19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libclang1-19 1:19.1.7-3+b1 No fix yet | 0.5% 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-2026-41080 | LOW3.15 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30t64 3.8.9-3+deb13u2 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl-dev 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | llvm-19-dev 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | llvm-19-runtime 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39956 | LOW3.11 | jq 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57451 | LOW3.11 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1t64 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-55200 | LOW2.99 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56390 | LOW2.86 | bison 2:3.8.2+dfsg-1+b2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28417 | LOW2.81 | vim 2:9.1.1230-2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-39128 | LOW2.8 | gdb 16.3-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39129 | LOW2.8 | gdb 16.3-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-39130 | LOW2.8 | gdb 16.3-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33947 | LOW2.8 | jq 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43894 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47770 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54679 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-55892 | LOW2.8 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-59857 | LOW2.8 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-1000382 | LOW2.8 | vim 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32249 | LOW2.8 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | libclang-common-19-dev 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | libclang-common-19-dev 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | libclang-cpp19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | libclang-cpp19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | libclang1-19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | libclang1-19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd-dev 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd-dev 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd-shared 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd-shared 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | llvm-19-dev 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | llvm-19-dev 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | llvm-19-runtime 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | llvm-19-runtime 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6472 | LOW2.75 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3592 | LOW2.7 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5950 | LOW2.7 | bind9-dnsutils 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3592 | LOW2.7 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5950 | LOW2.7 | bind9-host 1:9.20.21-1~deb13u1 fixed in 1:9.20.23-1~deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33948 | LOW2.7 | jq 1.7.1-6+deb13u1 fixed in 1.7.1-6+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3t64-gnutls 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u2 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2-1t64 1.11.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.13-minimal 3.13.5-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4360 | LOW2.7 | python3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim 2:9.1.1230-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| 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-2008-4677 | LOW2.58 | vim 2:9.1.1230-2 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-16517 | LOW2.46 | libarchive13t64 3.7.4-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2-dev 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57452 | LOW2.4 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libglib2.0-0t64 2.84.4-3~deb13u2 fixed in 2.84.4-3~deb13u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.7.1-6+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6474 | LOW2.19 | postgresql-client-17 17.9-0+deb13u1 fixed in 17.10-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | vim 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-1010220 | LOW1.98 | tcpdump 4.99.5-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 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-2024-7883 | LOW1.89 | clang-19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-7883 | LOW1.89 | llvm-19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-7883 | LOW1.89 | llvm-19-linker-tools 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-7883 | LOW1.89 | llvm-19-tools 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 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-2007-3719 | LOW1.78 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13573 | LOW1.68 | clang-19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13574 | LOW1.68 | clang-19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9301 | LOW1.68 | cmake 3.31.6-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13573 | LOW1.68 | llvm-19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13574 | LOW1.68 | llvm-19 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13573 | LOW1.68 | llvm-19-linker-tools 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13574 | LOW1.68 | llvm-19-linker-tools 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13573 | LOW1.68 | llvm-19-tools 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13574 | LOW1.68 | llvm-19-tools 1:19.1.7-3+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11961 | LOW1.61 | libpcap0.8t64 1.10.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| 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-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 |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2002-1976 | LOW1.07 | net-tools 2.10-1.3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-47162 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34982 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52859 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-7738 | NONE0 | bash-completion 1:2.16.0-7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libpam-systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | systemd-sysv 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28417 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-28421 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39881 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52858 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52860 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55693 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55895 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57455 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57456 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59856 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-59858 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-15173 | NONE0 | nmap-common 7.95+dfsg-3 No fix yet | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-26269 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33412 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-25749 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-41411 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-35177 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46483 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libpam-systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | systemd-sysv 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28419 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | libc6-dbg 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58058 | NONE0 | nmap-common 7.95+dfsg-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libpam-systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libpam-systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | systemd 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | systemd-sysv 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | systemd-sysv 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57451 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57451 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-1000382 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32249 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28418 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45130 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55892 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59857 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-1000382 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32249 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc6-dbg 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-31437 | NONE0 | libpam-systemd 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libpam-systemd 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libpam-systemd 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd-sysv 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd-sysv 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd-sysv 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-44656 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-47167 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57452 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-28420 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-42307 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2008-4677 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2008-4677 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-53905 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-53905 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-53906 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dbg 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-4438 | NONE0 | libc6-dbg 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-9301 | NONE0 | cmake-data 3.31.6-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses-dev 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncurses6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libpam-systemd 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libpam-systemd 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-4539 | NONE0 | python3-pygments 2.18.0+dfsg-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd-sysv 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd-sysv 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-28422 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b8 No fix yet | — | Not Applicable |
| CVE-2026-56389 | NONE0 | bison 2:3.8.2+dfsg-1+b2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.7.1-2 fixed in 2.8.2-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-2+b1 fixed in 1.3.14-2+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-42798 | NONE0 | liblcms2-2 2.16-2 fixed in 2.16-2+deb13u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.13-stdlib 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31558 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31718 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31743 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43376 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43379 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43307 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46036 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46085 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46326 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63936 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64141 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64142 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64169 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64226 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64252 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64367 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64457 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64499 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64509 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31644 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43438 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46263 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46288 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46332 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | — | Not Applicable |
| CVE-2026-64248 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64250 | NONE0 | linux-libc-dev 6.12.74-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.13-minimal 3.13.5-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.13-minimal 3.13.5-2 fixed in 3.13.5-2+deb13u3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6879 | NONE0 | python3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43961 | NONE0 | vim 2:9.1.1230-2 No fix yet | — | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-common 2:9.1.1230-2 No fix yet | — | Not Applicable |
| CVE-2026-43961 | NONE0 | vim-runtime 2:9.1.1230-2 No fix yet | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.