Last scanned:
This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. The top findings are denial-of-service flaws: uncontrolled recursion in glibc (e.g., CVE-2019-9192) and unbounded memory growth in OpenSSL's QUIC handler (CVE-2026-34183), which an attacker could exploit to crash processes or exhaust memory. Although the image is an official Docker image (trust score 100) and post-exploit-only findings are low severity, the exposed surface includes 14 high-severity (≥7) issues with a max of 7.5. Applying the latest package updates for glibc, OpenSSL, and the Linux kernel headers would eliminate these top risks. Note that the OpenSSL issue only applies if QUIC is used, and the glibc issue requires crafted regex patterns, so exposure depends on the workload built on this base. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.12.88-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.12.88-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | HIGH7.5 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-10263 | HIGH7.14 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63797 | HIGH7.14 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | HIGH7 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18220 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-22069 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52969 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53097 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53098 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53119 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53143 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53233 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53234 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53272 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-53362 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53366 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63794 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63804 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64600 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.88-1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-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-2018-20712 | MEDIUM6.5 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.12.88-1 No fix yet | 80.3% Actively Exploited | 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-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-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46244 | MEDIUM6.21 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46203 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52968 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53179 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53346 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46117 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46316 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52951 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52976 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53202 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53203 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53277 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53360 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53398 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53399 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63795 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63824 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63829 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63830 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63831 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63875 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63884 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63886 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63887 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63888 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63899 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63917 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63921 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63922 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63924 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63939 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63952 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63956 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63962 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63970 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63993 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63994 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64007 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64009 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64017 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64018 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64026 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64051 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64061 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64099 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64113 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64132 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64137 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64191 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64217 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64265 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64268 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64271 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64276 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64277 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64287 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64296 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64303 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64304 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64364 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64375 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64378 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64382 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64383 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64385 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64387 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64434 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64483 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64490 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64534 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64552 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64556 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64558 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53031 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53110 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53132 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53182 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53192 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53193 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53209 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53235 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53260 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53341 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53361 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53381 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53384 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53388 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53391 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53392 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53397 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63800 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63801 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63802 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63807 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63808 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63809 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63823 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63826 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63883 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63889 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63891 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63894 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63896 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63898 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63901 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63912 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63913 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63914 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63916 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63918 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63919 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63920 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63925 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63928 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63938 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63940 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63941 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63944 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63945 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63946 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63947 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63957 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63958 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63971 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63975 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63978 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63979 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63984 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63987 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63992 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63996 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64000 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64001 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64002 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64011 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64015 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64024 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64025 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64029 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64032 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64034 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64047 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64048 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64053 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64068 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64098 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64102 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64109 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64111 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64114 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64115 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64117 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64119 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64136 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64160 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64174 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64189 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64192 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64216 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64247 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64251 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64255 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64266 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64280 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64283 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64286 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64298 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64305 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64306 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64312 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64317 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64319 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64320 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64321 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64322 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64323 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64324 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64340 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64341 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64342 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64354 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64355 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64372 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64377 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64379 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64380 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64384 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64401 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64402 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64414 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64418 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64422 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64448 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64456 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64470 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64471 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64473 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64475 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64481 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64508 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64515 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64520 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64523 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64525 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64527 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64530 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64531 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64539 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64543 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64548 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64551 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64554 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64557 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64559 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64560 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% 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-2025-1153 | MEDIUM5.9 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.88-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.12.88-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53094 | MEDIUM5.7 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64535 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.88-1 No fix yet | 0.6% 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-13716 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.12.88-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53033 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53081 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53085 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53092 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.12.88-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-52908 | MEDIUM4.93 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.12.88-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31435 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31562 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31732 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43272 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43325 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43326 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43331 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43337 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43346 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43485 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45845 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45930 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46096 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46207 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46211 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46216 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46256 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46313 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46315 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52941 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52961 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52964 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52967 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52977 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52980 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52996 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53013 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53014 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53022 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53023 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53032 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53034 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53035 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53038 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53048 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53051 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53052 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53058 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53069 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53070 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53084 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53096 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53101 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53105 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53123 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53126 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53140 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53142 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53144 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53151 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53152 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53154 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53163 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53180 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53183 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53184 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53190 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53191 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53205 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53207 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53210 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53214 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53241 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53251 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53252 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53261 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53271 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53274 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53279 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53288 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53291 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53293 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53298 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53317 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53318 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53321 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53327 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53328 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53331 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53336 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53343 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53345 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53347 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53350 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53365 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53376 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53377 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53379 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53382 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53385 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53393 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53394 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53400 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53402 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53403 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63798 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63803 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63822 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63832 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63838 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63842 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63850 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63852 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63858 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63860 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63865 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63867 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63868 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63870 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63890 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63892 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63893 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63897 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63900 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63902 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63903 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63904 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63906 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63926 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63927 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63937 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63942 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63943 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63948 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63961 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63963 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63968 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63969 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63976 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63980 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63983 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63985 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63995 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64004 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64005 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64006 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64012 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64014 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64036 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64038 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64046 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64052 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64058 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64059 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64063 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64064 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64065 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64067 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64073 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64076 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64077 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64079 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64103 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64106 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64112 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64116 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64118 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64121 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64123 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64125 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-64126 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64127 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64128 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64133 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64157 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64159 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64170 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64173 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64177 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64178 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64185 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64190 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64205 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64206 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64210 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64212 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64220 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64222 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64223 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64225 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64235 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64239 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64243 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64245 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64253 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64279 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64284 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64289 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64290 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64299 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64307 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64308 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64309 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64310 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64313 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64315 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64316 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64326 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64327 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64328 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64329 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64330 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64333 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64336 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64338 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64343 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64344 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64346 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64347 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64351 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64357 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64360 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64362 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64363 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64365 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64368 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64369 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64373 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64374 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64381 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64403 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64404 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64405 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64406 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64407 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64408 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64409 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64411 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64412 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64413 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64416 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64423 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64424 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64433 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64436 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64452 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64454 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64455 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64458 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64463 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64472 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64477 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64478 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64479 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64487 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64496 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64507 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64510 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64517 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64524 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64529 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64540 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64541 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64542 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64545 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64546 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64547 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64553 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64555 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46201 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52974 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63810 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63821 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63843 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63844 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63845 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63851 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63853 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63869 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63871 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63872 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63876 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63877 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63929 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63964 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63973 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63974 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63990 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63991 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63997 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63998 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63999 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64003 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64039 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64060 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64062 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64066 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64070 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64078 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64105 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64131 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64134 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64144 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64146 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64153 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64155 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64158 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64163 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64179 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64180 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64182 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64183 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64184 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64187 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64213 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64214 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64227 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64231 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64232 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64237 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64244 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64254 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64256 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64275 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64294 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64297 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64301 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64332 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64334 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64335 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64352 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64370 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64376 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64388 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64415 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64417 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64419 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64428 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64430 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64435 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64465 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64474 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64476 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64480 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64482 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64486 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64488 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64489 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64511 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64512 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64513 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64514 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64519 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64537 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64544 | MEDIUM4.67 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64538 | MEDIUM4.5 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23469 | MEDIUM4 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18220 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.88-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | 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-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 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-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-34181 | LOW3.21 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.41-12+deb13u3 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-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.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-4609 | LOW2.94 | linux-libc-dev 6.12.88-1 No fix yet | 32.1% High Exploitation Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 6.12.88-1 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19449 | LOW2.81 | linux-libc-dev 6.12.88-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 6.12.88-1 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46300 | LOW2.81 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 6.12.88-1 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25265 | LOW2.81 | linux-libc-dev 6.12.88-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% 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-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-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-66861 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW2.78 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | LOW2.57 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-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-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-2018-20712 | LOW2.34 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW2.34 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53383 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53386 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53387 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53389 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53390 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63812 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63817 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63833 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63861 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63862 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63881 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63882 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63909 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63936 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63949 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64033 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64108 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64141 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64142 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64147 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64148 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64164 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64166 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64169 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64226 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64233 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64240 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64246 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64252 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64358 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64367 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64386 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64421 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64457 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64493 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64499 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64509 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64518 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.96-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-64248 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64250 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.