This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could remotely trigger denial of service, information disclosure, or memory corruption via vulnerable libraries such as GnuTLS (CVE-2026-33845) and PCRE2 (CVE-2025-58050). The OpenSSL vulnerability (CVE-2026-45445) only affects applications using the low-level EVP_Cipher() API, which is rare, reducing practical exposure. Network segmentation and restricting unnecessary services can mitigate some risks, but the sheer volume of high-severity issues demands caution. Note that many findings require no authentication, increasing the attack surface if the container is exposed to untrusted networks.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-33845 | HIGH7.73 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | HIGH7.73 | libpcre2-16-0 10.45-1 fixed in 10.46-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | HIGH7.73 | libpcre2-32-0 10.45-1 fixed in 10.46-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | HIGH7.73 | libpcre2-8-0 10.45-1 fixed in 10.46-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | HIGH7.73 | libpcre2-dev 10.45-1 fixed in 10.46-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-58050 | HIGH7.73 | libpcre2-posix3 10.45-1 fixed in 10.46-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.40 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-8 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-8 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-8 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-8 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-8 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-8 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-8 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-8 No fix yet | 2.4% 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-2020-36325 | HIGH7.5 | libjansson4 2.14-2+b3 No fix yet | 1.7% 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-2026-33416 | HIGH7.5 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33416 | HIGH7.5 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u4 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9900 | HIGH7.48 | libtiff6 4.7.0-3 fixed in 4.7.0-3+deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32990 | MEDIUM6.97 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-5745 | MEDIUM6.88 | libc-bin 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.41-8 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5745 | MEDIUM6.88 | libc-dev-bin 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-dev-bin 2.41-8 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5745 | MEDIUM6.88 | libc6 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.41-8 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5745 | MEDIUM6.88 | libc6-dev 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.41-8 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-25646 | MEDIUM6.88 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u3 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.6% 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-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-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-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-1 No fix yet | 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-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses-dev 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.40 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22801 | MEDIUM6.63 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u2 | 0.1% 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-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM6.63 | libtiff6 4.7.0-3 fixed in 4.7.0-3+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u2 | 0.3% 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 | 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 | 2.8% 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 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.7.0-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-33636 | MEDIUM6.46 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u4 | 0.6% 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-45186 | MEDIUM6.38 | libexpat1 2.7.1-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6052 | MEDIUM6.38 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.3-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33846 | MEDIUM6.38 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-42009 | MEDIUM6.38 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.8% 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-27135 | MEDIUM6.38 | libnghttp2-14 1.64.0-1.1 fixed in 1.64.0-1.1+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.40 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.40 5.40.1-3 No fix yet | 0.4% 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-2025-69421 | MEDIUM6.38 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3 No fix yet | 0.3% 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.2% 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.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.3% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64720 | MEDIUM6.03 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-65018 | MEDIUM6.03 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66293 | MEDIUM6.03 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22695 | MEDIUM6.03 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u2 | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.75-8 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | 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-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-2025-9231 | MEDIUM5.9 | libssl3t64 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9231 | MEDIUM5.9 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3t64 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-2 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.41-8 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-dev-bin 2.41-8 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.41-8 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.41-8 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-6395 | MEDIUM5.52 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.40 5.40.1-3 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.5% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | MEDIUM5.52 | openssl-provider-legacy 3.5.0-2 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 | 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-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-8 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.7.1-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-32989 | MEDIUM5.3 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3 | 1.2% Low-Moderate Risk | 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-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | MEDIUM5.18 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-64506 | MEDIUM5.18 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.1% 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-11187 | MEDIUM5.18 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11187 | MEDIUM5.18 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.41-8 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-dev-bin 2.41-8 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.41-8 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.41-8 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.7.1-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% 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-2026-40355 | MEDIUM5.02 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM5.02 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% 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-2026-40355 | MEDIUM5.02 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-40909 | MEDIUM5.02 | libperl5.40 5.40.1-3 fixed in 5.40.1-5 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15468 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-66199 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.2-1 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | libc-bin 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | libc-dev-bin 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | libc6 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5702 | MEDIUM4.76 | libc6-dev 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.7% 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.2% 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.2% 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.2% 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-66382 | MEDIUM4.67 | libexpat1 2.7.1-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-1 No fix yet | 0.1% 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.2% 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-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.48-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1 No fix yet | 0.5% 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.2% 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-2025-15469 | MEDIUM4.67 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3 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-2025-15469 | MEDIUM4.67 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% 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 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.40 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-6965 | MEDIUM4.58 | libsqlite3-0 3.46.1-6 fixed in 3.46.1-7 | 64.9% Actively Exploited | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.8-1 No fix yet | 8.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.8-1 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.41-8 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.41-8 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-dev-bin 2.41-8 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-dev-bin 2.41-8 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.41-8 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.41-8 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.41-8 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.41-8 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.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-23865 | MEDIUM4.5 | libfreetype6 2.13.3+dfsg-1 fixed in 2.13.3+dfsg-1+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30t64 3.8.9-2 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.6% 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-34743 | MEDIUM4.5 | liblzma-dev 5.8.1-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 No fix yet | 0.4% 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-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng-dev 1.6.48-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.6% 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 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-47162 | MEDIUM4.49 | vim-common 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-47162 | MEDIUM4.49 | vim-tiny 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-6 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.6% 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.5% 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-42250 | MEDIUM4.25 | libbz2-dev 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.6% 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.5% 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.6% 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.5% 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.6% 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.5% 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-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.40 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.6% 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.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34982 | MEDIUM4.18 | vim-common 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-common 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34982 | MEDIUM4.18 | vim-tiny 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-52859 | MEDIUM4.18 | vim-tiny 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 48.7% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 48.7% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 48.7% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 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-2025-68160 | MEDIUM4 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-8 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-8 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-8 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-8 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-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 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-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.40 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-common 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28421 | LOW3.98 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-39881 | LOW3.98 | vim-tiny 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-52858 | LOW3.98 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-52860 | LOW3.98 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-common 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-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-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 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-5773 | LOW3.82 | libcurl4t64 8.14.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4t64 8.14.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW3.82 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.40 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.40 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-common 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-26269 | LOW3.82 | vim-tiny 2:9.1.1230-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-64505 | LOW3.74 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng-dev 1.6.48-1 fixed in 1.6.48-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64505 | LOW3.74 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16t64 1.6.48-1 fixed in 1.6.48-1+deb13u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33412 | LOW3.72 | vim-common 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-common 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33412 | LOW3.72 | vim-tiny 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-25749 | LOW3.72 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41411 | LOW3.72 | vim-tiny 2:9.1.1230-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.25.0-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| 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.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-35177 | LOW3.62 | vim-tiny 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-46483 | LOW3.57 | vim-common 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-46483 | LOW3.57 | vim-tiny 2:9.1.1230-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.41-8 fixed in 2.41-11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc-dev-bin 2.41-8 fixed in 2.41-11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.41-8 fixed in 2.41-11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.41-8 fixed in 2.41-11 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1484 | LOW3.57 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| 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-common 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-2025-9231 | LOW3.54 | openssl 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-1 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13034 | LOW3.47 | libcurl4t64 8.14.1-1 fixed in 8.14.1-2+deb13u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4t64 8.14.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4t64 8.14.1-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.41-8 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-dev-bin 2.41-8 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.41-8 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.41-8 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3t64 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28419 | LOW3.37 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28419 | LOW3.37 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9230 | LOW3.36 | openssl 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-11563 | LOW3.31 | libcurl4t64 8.14.1-1 fixed in 8.14.1-2+deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4t64 8.14.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4t64 8.14.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4t64 8.14.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4t64 8.14.1-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-2673 | LOW3.31 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.40.1-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.40 5.40.1-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| 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-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 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-2026-3805 | LOW3.21 | libcurl4t64 8.14.1-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.4% 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-2025-9086 | LOW3.18 | libcurl4t64 8.14.1-1 fixed in 8.14.1-2+deb13u1 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-8 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-8 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-8 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.41-8 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.7.1-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7039 | LOW3.15 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3832 | LOW3.15 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% 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-common 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-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11187 | LOW3.11 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libssl3t64 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15468 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-66199 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl 5.40.1-3 fixed in 5.40.1-5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-base 5.40.1-3 fixed in 5.40.1-5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-40909 | LOW3.01 | perl-modules-5.40 5.40.1-3 fixed in 5.40.1-5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14087 | LOW3 | libglib2.0-0t64 2.84.2-1 fixed in 2.84.4-3~deb13u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42010 | LOW3 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3+deb13u4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.40 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | libssl3t64 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.40 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-32988 | LOW2.95 | libgnutls30t64 3.8.9-2 fixed in 3.8.9-3 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-provider-legacy 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4t64 8.14.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-35331 | LOW2.81 | libtcl8.6 8.6.16+dfsg-1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | LOW2.81 | vim-common 2:9.1.1230-2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28417 | LOW2.81 | vim-tiny 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.2% 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-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 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.2% 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-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15469 | LOW2.8 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-1 No fix yet | 0.7% 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-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-1000382 | LOW2.8 | vim-common 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32249 | LOW2.8 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28418 | LOW2.8 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-45130 | LOW2.8 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-1000382 | LOW2.8 | vim-tiny 2:9.1.1230-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32249 | LOW2.8 | vim-tiny 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 | libcairo2 1.18.4-1+b1 No fix yet | 0.2% 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-2025-6141 | LOW2.8 | libncurses-dev 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-3 No fix yet | 0.5% 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-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff6 4.7.0-3 fixed in 4.7.0-3+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff6 4.7.0-3 fixed in 4.7.0-3+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | perl 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% 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 | libcurl4t64 8.14.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4t64 8.14.1-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4t64 8.14.1-1 No fix yet | 0.4% 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.0-2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.40.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.40 5.40.1-3 No fix yet | 0.2% 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-common 2:9.1.1230-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-44656 | LOW2.7 | vim-tiny 2:9.1.1230-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-47167 | LOW2.7 | vim-tiny 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 No fix yet | 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.5% 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.6% 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.5% 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.6% 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.5% 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.6% 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.5% 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.6% 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.5% 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.6% Theoretical Threat | Directly Exposed |
| CVE-2008-4677 | LOW2.58 | vim-common 2:9.1.1230-2 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-4677 | LOW2.58 | vim-tiny 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.6% 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.5% 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-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 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.6% 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.5% 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-34180 | LOW2.55 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.40 5.40.1-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.40 5.40.1-3 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-2025-10148 | LOW2.45 | libcurl4t64 8.14.1-1 fixed in 8.14.1-2+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-1 No fix yet | 0.1% 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-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-1 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-2025-68160 | LOW2.4 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 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.2-1 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-5278 | LOW2.24 | coreutils 9.7-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-common 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28420 | LOW2.24 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42307 | LOW2.24 | vim-tiny 2:9.1.1230-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff6 4.7.0-3 fixed in 4.7.0-3+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-53905 | LOW2.09 | vim-common 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | vim-common 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-53905 | LOW2.09 | vim-tiny 2:9.1.1230-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-53906 | LOW2.09 | vim-tiny 2:9.1.1230-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69418 | LOW2.04 | openssl 3.5.0-2 fixed in 3.5.4-1~deb13u2 | 0.1% Theoretical Threat | 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-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.5.0-2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-9232 | LOW1.86 | openssl 3.5.0-2 fixed in 3.5.1-1+deb13u1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| 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-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 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-2011-4116 | LOW1.68 | perl 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-29 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.5% 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.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% 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.5% 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.6% 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-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 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-common 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-28422 | LOW1.12 | vim-tiny 2:9.1.1230-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc-l10n 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-23112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010022 | NONE0 | locales 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-l10n 2.41-8 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-43037 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23395 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | locales 2.41-8 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-31788 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5745 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-5745 | NONE0 | locales 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-0861 | NONE0 | locales 2.41-8 fixed in 2.41-12+deb13u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules 1.7.0-3 fixed in 1.7.0-5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.7.0-3 fixed in 1.7.0-5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.7.0-3 fixed in 1.7.0-5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.7.0-3 fixed in 1.7.0-5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libsystemd0 257.6-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-29111 | NONE0 | libudev1 257.6-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-57995 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58093 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37803 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38087 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38101 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38106 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38109 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38118 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38131 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38141 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38146 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38154 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38157 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38172 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38179 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38183 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38198 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38201 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38211 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38212 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38216 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38226 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38227 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38230 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38236 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38239 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38245 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38250 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38257 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38259 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38267 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38270 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38279 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38280 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38288 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38289 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38295 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38298 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38313 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38317 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38323 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38338 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38341 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38346 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38348 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38349 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38350 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38352 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2025-38361 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38375 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38377 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38385 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38389 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38396 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38401 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38403 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38415 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38416 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38422 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38423 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38425 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38428 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38437 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38443 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38456 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38459 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38464 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38471 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38476 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38484 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38485 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38488 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38490 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38494 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38500 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38512 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38527 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38533 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38535 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38538 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38548 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38550 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38552 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38555 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38563 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38565 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38568 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38572 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38574 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38579 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38584 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38593 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38618 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38627 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38653 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38662 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38666 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38676 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38685 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38688 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38697 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38699 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38702 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38703 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38704 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38707 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38708 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38718 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38724 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38729 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38730 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39686 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39689 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39691 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39701 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39711 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39723 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39727 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39730 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39738 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39743 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39766 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39776 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39783 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39788 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39790 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39823 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39824 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39828 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39835 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39836 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39841 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39849 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39854 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39860 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39861 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39863 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39864 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39866 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39870 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39871 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39873 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39877 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39880 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39881 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39882 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39896 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39911 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39913 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39917 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39944 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39945 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39951 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39955 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39957 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39963 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39967 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40149 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68817 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71071 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71075 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71078 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71082 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71086 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71089 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71091 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71099 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71100 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71122 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71137 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71143 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71156 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71157 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71162 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71234 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71238 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22980 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23001 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23010 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23013 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23025 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23068 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23073 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23074 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23078 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23083 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23089 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23098 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23156 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23158 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23193 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23209 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23216 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23221 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23223 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23224 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23227 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-23233 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23234 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23319 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23343 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23354 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23359 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23387 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23390 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23408 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23410 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23411 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23412 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23413 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23422 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23427 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31399 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31402 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31431 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 75.5% Actively Exploited | Not Applicable |
| CVE-2026-31452 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31455 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31474 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31485 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31488 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31489 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31500 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31506 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31530 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31532 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31566 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31576 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31578 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31580 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31581 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31582 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31583 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31686 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31696 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31702 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31709 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31715 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31720 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31730 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31731 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31747 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31748 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31759 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31787 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43007 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43015 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43020 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43027 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43120 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43128 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43138 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43150 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43178 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43196 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43205 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43260 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43284 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 92.2% Actively Exploited | Not Applicable |
| CVE-2026-43328 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43378 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43426 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43458 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43500 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 94.0% Actively Exploited | Not Applicable |
| CVE-2026-45946 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45984 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45989 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45996 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45998 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46001 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46004 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46047 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46162 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46163 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46189 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46234 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46243 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46246 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46267 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46300 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46333 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2025-40047 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40258 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40277 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.7% 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-2025-39971 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-l10n 2.41-8 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-l10n 2.41-8 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2025-38501 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-38566 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-22998 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43501 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46195 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-39973 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39982 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40240 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68349 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31669 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43110 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43186 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | locales 2.41-8 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | locales 2.41-8 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam-modules 1.7.0-3 fixed in 1.7.0-5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam-modules-bin 1.7.0-3 fixed in 1.7.0-5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam-runtime 1.7.0-3 fixed in 1.7.0-5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-10963 | NONE0 | libpam0g 1.7.0-3 fixed in 1.7.0-5 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68305 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-4055 | NONE0 | xdg-utils 1.2.1-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-31607 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43038 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39984 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40141 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40176 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40269 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40294 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40304 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68741 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68800 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23243 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43074 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43078 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22121 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38088 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38103 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38110 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38139 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38153 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38159 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38224 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38249 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38286 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38320 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38342 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38395 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38445 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38446 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38482 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38483 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38497 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38502 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38521 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38529 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38530 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38556 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38652 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38670 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38677 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38679 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38680 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38713 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38714 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38715 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38728 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38736 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39682 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39683 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39685 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39687 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39710 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39719 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39750 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39757 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39760 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39761 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39806 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39817 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39839 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39853 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39869 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39883 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39891 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39922 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39943 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40082 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71093 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71101 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71116 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71133 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71136 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22984 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23076 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23099 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23187 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23204 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23235 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23244 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23315 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23318 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23325 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23363 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23388 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23397 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31430 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31614 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31778 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43040 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43052 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43141 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43241 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43281 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43380 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43386 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43427 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43449 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43450 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43453 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45994 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46022 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46033 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46191 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40246 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40301 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40322 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40349 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40351 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68168 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68347 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68356 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68357 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68366 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68724 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68811 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23455 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31685 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31786 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43051 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43056 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43330 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46053 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46056 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46120 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46150 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46155 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46209 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46259 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-38102 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38108 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39702 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39749 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39759 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39826 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39966 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40186 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40248 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68287 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71203 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71221 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23454 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43050 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43329 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43494 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43503 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45852 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45898 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45972 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46099 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46116 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46145 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46152 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46166 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46176 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46227 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39993 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40096 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40133 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40135 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40154 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40199 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40216 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40259 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40271 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40318 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68285 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68301 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23270 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23392 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31408 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31508 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31586 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31694 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31772 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43023 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43158 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43226 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43233 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43304 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43332 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43334 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43339 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43341 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43493 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45856 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45860 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-45861 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45886 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45910 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45912 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45970 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46015 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46043 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46052 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46069 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46076 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46084 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46114 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46119 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46121 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46132 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46133 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46139 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46149 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46173 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46174 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46185 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46251 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46294 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46306 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23054 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40345 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68346 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libsystemd0 257.6-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-4105 | NONE0 | libudev1 257.6-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40024 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40257 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68167 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68237 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45837 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40018 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40261 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45991 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-l10n 2.41-8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68284 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-39969 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40061 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40273 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68354 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68362 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68380 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23179 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31470 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31588 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4437 | NONE0 | locales 2.41-8 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | locales 2.41-8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-27748 | NONE0 | xdg-utils 1.2.1-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-40225 | NONE0 | libsystemd0 257.6-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libsystemd0 257.6-1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40225 | NONE0 | libudev1 257.6-1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-40226 | NONE0 | libudev1 257.6-1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39978 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40309 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40321 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40350 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68371 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23178 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23450 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23456 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31525 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40000 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40302 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40320 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68282 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31504 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40048 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40052 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40132 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40147 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68757 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71066 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23253 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40019 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40038 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40080 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40279 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68245 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68343 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68764 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68770 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68815 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68819 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31449 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31464 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31511 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31570 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31700 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31708 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43044 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43134 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% 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-2025-40359 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31649 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-l10n 2.41-8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40083 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40230 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40242 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40324 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23246 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5435 | NONE0 | locales 2.41-8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-15281 | NONE0 | locales 2.41-8 fixed in 2.41-12+deb13u2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39975 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39994 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39998 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40118 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40142 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40167 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40194 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40201 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40203 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40214 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40237 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40272 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40323 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40329 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40340 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68199 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68742 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23271 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23317 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31392 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31414 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31426 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43279 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46065 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46113 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40319 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46024 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5702 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36350 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36357 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68801 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68816 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5702 | NONE0 | locales 2.41-8 fixed in 2.41-9 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40347 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68192 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68215 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68297 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68307 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58091 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21709 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21751 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21807 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21833 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21884 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22101 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22105 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22106 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22116 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22117 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22119 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22122 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.33-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.33-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22124 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22128 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23137 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23155 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37925 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37984 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38067 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38084 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38086 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38089 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38090 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38093 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38100 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38105 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38113 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38115 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38119 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38120 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38122 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38124 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38126 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38134 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38135 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38136 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38138 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38142 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38143 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38145 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38147 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38148 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38149 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38151 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38155 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38156 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38158 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38160 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38161 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38162 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38163 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38164 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38165 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38166 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38167 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38168 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38169 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38170 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38173 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38174 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.33-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38181 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38184 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38185 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38186 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38188 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38189 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38191 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38192 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38193 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38194 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38197 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38202 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38208 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38210 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38214 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38215 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38218 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38219 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38222 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38223 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38225 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38228 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38229 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38251 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38253 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38255 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38256 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38258 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38260 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38262 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38263 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38265 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.33-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38268 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38269 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38273 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38274 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38275 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38277 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38278 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38282 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38285 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38290 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38293 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38297 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38299 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38300 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38301 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38302 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38303 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38304 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38305 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38307 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38310 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38312 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38315 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38318 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38319 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38321 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38322 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38324 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38325 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38326 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38328 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38331 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38332 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38334 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38335 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38336 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38337 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38343 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38344 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38345 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38347 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38351 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38353 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38354 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38355 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38356 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38360 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38362 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38363 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38364 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38368 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38371 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38372 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38373 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38374 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38376 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38379 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38381 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38382 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38384 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38386 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38387 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38388 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38390 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38391 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38392 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38399 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38400 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38402 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38404 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38405 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38406 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38407 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38408 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38409 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38410 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38412 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38413 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38414 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38417 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38418 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38419 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38420 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38424 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38427 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38430 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38434 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38436 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38439 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38441 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38444 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38450 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38451 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38452 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38453 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38454 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38455 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38457 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38458 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38460 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38463 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38465 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38466 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38467 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38468 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38469 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38470 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38472 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38473 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38474 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38475 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38478 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38480 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38481 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38487 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38489 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38491 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38493 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38495 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38496 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38498 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38499 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38503 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38505 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38506 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38510 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38511 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38513 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38514 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38516 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38517 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38520 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38523 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38526 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38528 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38532 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38537 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38539 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38540 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38541 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38542 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38543 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38545 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38546 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38547 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38549 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38551 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38557 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38559 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38560 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38562 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 7.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-38569 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38571 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38573 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38576 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38577 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38578 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38581 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38583 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38586 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38587 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38588 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38591 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38601 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38602 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38604 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38608 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38609 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38610 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38612 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38614 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38619 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38622 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38623 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38624 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38625 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38626 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38628 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38630 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38631 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38634 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38635 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38639 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38640 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38643 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38644 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38645 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38646 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38648 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38650 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38659 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38660 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38663 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38664 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38665 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38668 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38671 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38678 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38683 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38684 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38686 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38691 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38693 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38694 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38695 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38696 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38698 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38700 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38701 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38706 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38710 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38711 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38712 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38721 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38723 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38725 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38726 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38727 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38732 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38733 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38735 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38737 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39675 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39676 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39678 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39679 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39681 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39684 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39692 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39693 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39694 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39695 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39698 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39700 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39703 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39706 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39709 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39712 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39714 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39715 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39716 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39718 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39721 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39722 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39724 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39725 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39731 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39734 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39736 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39737 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39739 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39742 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39748 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39752 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39753 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39756 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39758 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39763 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39764 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39765 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39770 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39772 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39773 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39780 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39781 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39782 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39787 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39791 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39792 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39794 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39795 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39798 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39800 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39801 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39805 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39807 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39808 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39811 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39812 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39815 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39816 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39819 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39827 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39831 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39832 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39838 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39842 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39843 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39844 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39845 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39846 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39847 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39848 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39852 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39857 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39865 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39872 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39876 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39885 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39890 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39894 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39895 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39897 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39899 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39900 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39902 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39903 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39907 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39909 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39912 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39914 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39916 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39918 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39920 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39923 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39926 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39929 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39931 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39934 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39937 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39938 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39942 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39946 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 9.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39948 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39949 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39950 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39953 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39956 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39965 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40005 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40009 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40020 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40026 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40027 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40029 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40030 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40031 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40037 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40040 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40044 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40051 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40053 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40070 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40078 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40104 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40109 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40115 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40140 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40153 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40155 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40164 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40171 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40181 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40195 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40211 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40239 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40251 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40264 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40280 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40283 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40284 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40287 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40293 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40297 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40300 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40362 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40363 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68176 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68179 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68185 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68208 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68211 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68213 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68223 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68229 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68259 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68261 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68265 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68283 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68293 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68310 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68313 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68331 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68333 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68337 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68340 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68351 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68358 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68365 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68372 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68725 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68756 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68774 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68776 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68784 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68803 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68814 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68821 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68823 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71064 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71072 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71076 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71077 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71079 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71080 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71081 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71083 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71084 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71085 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71087 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71088 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71094 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71095 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71096 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71097 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71098 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71102 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71104 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71105 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71108 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71113 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71114 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71118 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71119 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71120 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71121 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71126 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71127 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71130 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71131 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71132 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71134 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71135 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71144 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71146 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71147 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71150 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71151 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71153 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71154 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71161 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71163 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71182 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71183 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71185 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71186 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71189 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71191 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71204 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71222 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71223 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71229 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71232 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71233 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71235 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71236 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71237 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71239 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71268 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71269 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71270 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71286 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71287 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71288 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71291 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71294 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71295 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71297 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71300 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71305 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71314 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22976 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22977 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22979 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22981 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22982 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22985 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22989 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22990 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22991 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22992 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-22993 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22994 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22997 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-22999 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23002 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23003 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23005 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23006 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23011 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23019 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23020 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23021 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23023 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23026 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23031 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23038 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23047 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23057 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23058 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23059 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23060 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23061 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23062 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23063 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23064 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23065 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23066 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23069 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23070 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23072 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23075 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23080 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23084 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23085 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23086 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23087 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23090 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23091 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23093 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23094 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23095 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23096 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23097 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23100 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23103 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23104 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23105 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23108 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23113 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23116 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23119 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23120 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23121 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23124 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23128 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23131 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23133 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23135 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23136 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23139 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23140 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23141 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23142 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23144 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23145 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23146 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23148 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23150 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23151 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23154 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23157 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23159 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23160 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23163 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23164 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23166 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23168 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23170 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23172 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23173 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23177 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23188 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23189 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23198 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23199 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23201 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23202 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23205 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23206 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23215 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23219 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23222 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23228 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23229 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23230 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23236 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23237 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23238 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23242 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23249 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23250 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23251 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23252 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23254 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23255 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23256 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23257 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23258 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23260 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23262 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23264 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23266 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23267 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23273 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23274 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23277 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23278 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23286 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23287 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23289 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23290 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23293 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23296 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23297 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23298 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23300 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23303 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23304 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23306 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23307 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23308 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23310 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23312 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23313 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23316 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23321 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23335 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23336 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23340 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23351 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23352 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23357 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23360 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23362 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23365 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23367 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23368 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23369 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23370 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23373 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23375 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23379 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23380 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23381 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23382 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23386 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23389 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23391 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23398 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23399 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23401 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23403 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23404 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23405 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23409 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23414 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23417 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23420 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23434 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23439 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23442 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23444 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23445 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23449 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23461 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23462 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-23464 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23466 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23470 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23475 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31394 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31400 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31403 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31406 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31407 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31411 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31415 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31416 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31421 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31422 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31423 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31424 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31425 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31427 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31428 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31429 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31434 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31436 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31438 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31439 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31440 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31441 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31446 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31447 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31448 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31450 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31451 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31453 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31454 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31467 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31469 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31473 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31479 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31480 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31482 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31483 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31492 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31495 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31496 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31497 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31498 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31499 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31503 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31507 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31509 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31510 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31512 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31515 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31518 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31519 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31520 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31521 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31522 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31524 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31528 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31533 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31540 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31542 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31545 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31546 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31548 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31549 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31550 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31551 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31552 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31554 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31555 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31556 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31559 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31561 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31565 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31575 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31577 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31585 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31590 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31593 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31594 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31595 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31596 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31599 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31603 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31604 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31605 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31615 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31616 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31617 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31618 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31619 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31623 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31624 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31625 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31628 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31634 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31637 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31638 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31639 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31642 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31645 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31646 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31647 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31651 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31658 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31660 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31661 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31662 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31664 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31665 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31666 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31667 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31670 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31671 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31672 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31673 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31674 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31676 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31678 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31679 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31680 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31681 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31682 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31684 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31687 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31689 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31693 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31698 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31699 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31701 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31704 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31714 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31721 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31726 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31732 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31733 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31736 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31737 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31738 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31739 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31740 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31741 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31749 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31752 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31754 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31755 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31756 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31758 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31762 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31763 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31765 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31770 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31773 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31774 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31779 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31781 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43012 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43013 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43014 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43017 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43018 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43019 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43024 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43025 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43026 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43028 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43032 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43033 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43035 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43041 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43043 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43046 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43054 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43057 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43058 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43059 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43060 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43061 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43062 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43063 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43064 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43065 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43066 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43068 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43069 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43071 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43072 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43077 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43079 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43080 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43081 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43082 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43085 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43086 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43089 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43090 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43092 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43093 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43094 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43098 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43099 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43103 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43104 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43105 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43108 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43109 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43113 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43114 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43124 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43130 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43132 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43133 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43135 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43136 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43139 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43140 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43143 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43145 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43147 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43148 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43149 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43152 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43156 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43157 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43159 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43162 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43168 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43169 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43171 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43175 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43177 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43182 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43183 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43187 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43189 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43199 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43201 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43202 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43209 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43210 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43214 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43218 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43221 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43223 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43225 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43227 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43229 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43230 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43238 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43240 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43242 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43243 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43246 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43251 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43252 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43255 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43257 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43261 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43262 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43264 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43265 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43266 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43268 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43269 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43270 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43273 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43277 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43278 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43287 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43289 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43293 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43295 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43296 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43297 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43300 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43302 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43306 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43312 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43313 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43314 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43315 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43316 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43319 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43320 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43327 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43333 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43340 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43343 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43345 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43350 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43354 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43357 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43359 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43360 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43361 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43363 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43365 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43366 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43372 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43374 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43381 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43382 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43387 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43392 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43393 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43394 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43395 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43397 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43403 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43405 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43406 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43407 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43408 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43411 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43412 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43420 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43421 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43424 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43425 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43428 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43429 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43432 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43436 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43437 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43441 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43444 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43445 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43451 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43452 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43455 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43457 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43459 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43466 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43467 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43468 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43469 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43470 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43471 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43472 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43473 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43475 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43486 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43492 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43502 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45834 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45835 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45836 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45857 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45862 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45891 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45914 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45947 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45948 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45950 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45954 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45960 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45962 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45964 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45965 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45968 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45969 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45973 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45974 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45976 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45978 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45982 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45983 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45986 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45987 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45997 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45999 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46002 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46003 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46005 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46007 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46009 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46016 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46018 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46019 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46021 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46023 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46026 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46027 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46028 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46034 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46037 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46038 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46040 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46041 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46046 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46048 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46049 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46050 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46051 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46061 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46063 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46064 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46070 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46078 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46079 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46082 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46086 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46093 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46094 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46102 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46106 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46115 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46127 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46138 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46144 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46146 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46151 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46161 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46165 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46167 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46168 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46169 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46172 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46179 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46184 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46186 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46188 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46193 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46196 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46207 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46214 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46216 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46235 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46247 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46249 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46253 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46255 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46260 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46261 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46262 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46273 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46280 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46283 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46289 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46291 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46304 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46307 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46329 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-14027 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40010 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40042 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40049 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40088 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40092 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40094 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40099 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40100 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40103 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40105 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40125 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40159 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40169 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40205 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40219 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40235 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40253 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40346 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40360 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68170 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68171 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68173 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68178 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68186 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68194 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68198 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68204 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68206 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68207 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68218 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68222 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68227 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68233 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68244 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68288 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68295 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68298 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68306 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68308 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68317 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68321 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68329 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68336 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68341 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68345 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68348 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68363 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68732 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68734 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68753 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68758 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68778 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68780 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68783 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68785 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68792 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68795 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68798 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68802 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68813 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68818 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68820 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71194 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43030 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43194 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43211 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43483 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43484 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43487 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43488 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43496 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45847 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45851 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45863 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45868 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45870 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45871 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45872 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45873 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45880 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45888 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45895 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45900 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45904 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45905 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45911 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45913 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45915 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45919 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45920 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45922 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45923 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45925 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45933 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45941 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46083 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46088 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46089 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46092 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46101 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46103 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46126 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46131 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46136 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46140 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46178 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46201 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46292 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46299 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46313 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46327 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 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-0915 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-l10n 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-l10n 2.41-8 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd0 257.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd0 257.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd0 257.6-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.6-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39968 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39972 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40058 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40204 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40212 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40353 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68367 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23053 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23457 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-0915 | NONE0 | locales 2.41-8 fixed in 2.41-12+deb13u2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-4046 | NONE0 | locales 2.41-8 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | locales 2.41-8 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | locales 2.41-8 No fix yet | 2.3% Low-Moderate Risk | 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-2025-39970 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40343 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40344 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40178 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-l10n 2.41-8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-l10n 2.41-8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40121 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-5450 | NONE0 | locales 2.41-8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | locales 2.41-8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% 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-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38083 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38085 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38104 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38217 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38232 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.35-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38242 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38306 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38365 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38383 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38393 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38440 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38448 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38461 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38462 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38477 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38515 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38561 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38617 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38632 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38675 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38681 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38687 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39673 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39697 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39713 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39813 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39825 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39884 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.48-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39977 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39980 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39992 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39996 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40006 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40011 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40016 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40039 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40056 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40085 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40110 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40120 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40134 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40179 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40187 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40197 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40215 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40238 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40244 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40250 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40252 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40254 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40331 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40342 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68214 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68239 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68241 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68312 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68361 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68749 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71111 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71274 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22986 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23071 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23101 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23110 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23126 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23161 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23167 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23169 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23210 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23212 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23302 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23440 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23441 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23452 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23463 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31389 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31393 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31456 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31466 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31523 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31697 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31728 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31751 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43047 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43163 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43275 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43342 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43383 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43415 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43430 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43439 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43448 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46159 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46187 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46194 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39991 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40357 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68181 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68264 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68374 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% 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-2019-15213 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40166 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40308 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40312 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68242 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40001 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40081 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40185 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40281 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40021 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40123 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40157 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40183 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40198 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40200 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23032 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23458 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31401 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40275 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8058 | NONE0 | locales 2.41-8 fixed in 2.41-11 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40173 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40218 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-l10n 2.41-8 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-4438 | NONE0 | libc-l10n 2.41-8 fixed in 2.41-12+deb13u3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40162 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | locales 2.41-8 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-4438 | NONE0 | locales 2.41-8 fixed in 2.41-12+deb13u3 | 0.2% 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-2020-35501 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68740 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd0 257.6-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd0 257.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.6-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68191 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-39964 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40035 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40341 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68744 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68746 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68775 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68782 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71148 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71224 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-22978 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23261 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31668 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% 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-2025-52968 | NONE0 | xdg-utils 1.2.1-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68788 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b2 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-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.22.20 fixed in 1.22.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.22.20 fixed in 1.22.21 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg-dev 1.22.20 fixed in 1.22.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg-dev 1.22.20 fixed in 1.22.21 | 0.3% Theoretical Threat | 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-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-2219 | NONE0 | libdpkg-perl 1.22.20 fixed in 1.22.22 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | libdpkg-perl 1.22.20 fixed in 1.22.21 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.7.1-1 No fix yet | — | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1 2.7.1-1 No fix yet | — | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-2+b1 No fix yet | 0.1% Theoretical Threat | 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-53615 | NONE0 | liblastlog2-2 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-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-3 No fix yet | 0.2% Theoretical Threat | 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-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.46.1-6 fixed in 3.46.1-7+deb13u1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2-1t64 1.11.1-1 No fix yet | — | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2-1t64 1.11.1-1 No fix yet | — | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2-1t64 1.11.1-1 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3 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-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23268 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31478 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31718 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43376 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43379 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.43-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.41-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39985 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39986 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39987 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39988 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39995 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40004 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40008 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40012 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40013 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40022 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40028 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40033 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40045 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40055 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40059 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40060 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40062 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40067 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40068 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40079 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40084 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40087 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40101 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40106 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40116 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40127 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40156 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40161 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40165 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40172 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40177 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40188 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40192 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40202 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40207 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40209 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40221 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40223 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40225 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40226 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40233 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40243 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40245 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40262 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40263 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40274 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40276 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40278 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40282 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40285 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40286 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40306 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40310 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40313 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40315 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40316 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40317 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40332 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68172 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68177 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68180 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68184 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68202 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68210 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68217 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68220 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68230 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68235 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68238 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68240 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68246 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68249 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.57-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68255 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68257 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68258 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68263 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68266 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68286 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68289 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68290 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68302 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68311 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68325 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68327 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68328 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68332 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68338 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68339 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68344 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68352 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68364 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68727 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68728 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68733 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68747 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68748 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68750 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.37-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68759 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68763 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68766 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.63-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68767 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68769 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68771 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68773 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68777 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68786 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68787 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68796 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68797 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68799 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68804 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68806 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68808 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68810 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71067 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71069 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71140 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71195 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71196 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71197 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71199 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71304 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71311 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23030 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23033 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23037 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23049 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23055 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23056 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.69-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23176 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23182 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.73-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23269 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23406 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23407 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.74-2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31433 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31476 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31477 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31563 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31584 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31644 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31695 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31743 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43222 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43256 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43291 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43307 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43324 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43368 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43377 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43384 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43438 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43476 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43480 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43482 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45848 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45849 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45853 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45864 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45865 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45866 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45867 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45869 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45874 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45875 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45878 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45879 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45881 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45882 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45883 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45884 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45885 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45890 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45902 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45916 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45921 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45924 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45928 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45935 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45936 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45938 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46011 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46036 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46073 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46074 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46085 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46142 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46326 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46332 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52904 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46263 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46286 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46287 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46288 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.86-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.88-1 | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | — | Not Applicable |
| CVE-2026-31558 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43212 | NONE0 | linux-libc-dev 6.12.32-1 fixed in 6.12.85-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52908 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | — | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.12.32-1 No fix yet | — | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.12.32-1 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 |
| CVE-2026-53615 | 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-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 |
| CVE-2026-53615 | 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-7010 | NONE0 | perl 5.40.1-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-3 No fix yet | 0.2% 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-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-53615 | NONE0 | util-linux 2.41-5 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-tiny 2:9.1.1230-2 No fix yet | — | Not Applicable |