This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. Specifically, an EXPOSED_SURFACE vulnerability, CVE-2025-69720, in the ncurses-base package, has a severity of 6.63 and could lead to arbitrary code execution if exploited. While there are 97 exposed vulnerabilities in total, CVE-2025-69720 is the most significant finding on the exposed surface. Furthermore, 453 post-exploit vulnerabilities are present, though none exceed a severity of 4.68, indicating a low risk for those requiring prior access. The image's status as an Official Docker Hub image, coupled with its digest pinning, provides a strong foundation of trust and immutability.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-69720 | MEDIUM6.63 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-41256 | MEDIUM5.5 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-41257 | MEDIUM5.5 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-43894 | MEDIUM5.5 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-43896 | MEDIUM5.5 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-44777 | MEDIUM5.5 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-40612 | MEDIUM5.5 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | — | Directly Exposed |
| CVE-2013-7445 | MEDIUM4.68 | linux-libc-dev 6.12.90-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46274 | MEDIUM4.68 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | MEDIUM4.67 | libjq1 1.7.1-6+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 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.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | MEDIUM4.49 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | MEDIUM4.49 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | MEDIUM4.4 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-46244 | MEDIUM4.38 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43414 | MEDIUM4.26 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2008-4609 | MEDIUM4.26 | linux-libc-dev 6.12.90-2 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45932 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46054 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46117 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46181 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43303 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45840 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45934 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46017 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46032 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46158 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46160 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46170 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46242 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46275 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2025-71313 | MEDIUM4.2 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2025-13151 | MEDIUM4.02 | libtasn1-6 4.20.0-2 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| 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-19449 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-19814 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-3847 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-21803 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58093 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38137 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38187 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38206 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38421 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39859 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39862 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39958 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31688 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12456 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-19378 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-11725 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-25265 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-26242 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3640 | LOW3.98 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-19070 | LOW3.82 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-0400 | LOW3.82 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-43197 | LOW3.66 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2021-45346 | LOW3.65 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22104 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38204 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38636 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23102 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23327 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40064 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31613 | LOW3.62 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3864 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40158 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40168 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43116 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1247 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-2961 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-45884 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-45885 | LOW3.57 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-1121 | LOW3.54 | linux-libc-dev 6.12.90-2 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-40130 | LOW3.47 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-36694 | LOW3.42 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6238 | LOW3.42 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.31 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6240 | LOW3.31 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68729 | LOW3.31 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW3.3 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-41257 | LOW3.3 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-43894 | LOW3.3 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-43896 | LOW3.3 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-44777 | LOW3.3 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-40612 | LOW3.3 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2025-71285 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2025-71289 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2025-71302 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43127 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43172 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43191 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43204 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43213 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43216 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43219 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43234 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43272 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43294 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43298 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43299 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43301 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43308 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43309 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43310 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43311 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43325 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43326 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43331 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43337 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43344 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43346 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43352 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43353 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43355 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43416 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43443 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43463 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43464 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-43465 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45838 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45841 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45842 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45843 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45844 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45845 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45846 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45944 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46066 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46093 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46130 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46137 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46252 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2025-71315 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45897 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45901 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45961 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-45963 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46014 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46059 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46071 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46092 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46153 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46203 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46216 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46256 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46279 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-46302 | LOW3.3 | linux-libc-dev 6.12.90-2 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44032 | LOW3.26 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44033 | LOW3.26 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3397 | LOW3.21 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40146 | LOW3.16 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40355 | LOW3.11 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68319 | LOW3.11 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-31879 | LOW3.11 | wget 1.25.0-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3714 | LOW3.01 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2004-0230 | LOW3 | linux-libc-dev 6.12.90-2 No fix yet | 9.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23039 | LOW2.91 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.7.1-6+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-37454 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-2193 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-25740 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52560 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56709 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58074 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58094 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58095 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21752 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21807 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21949 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22108 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22109 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22127 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23132 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23135 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37743 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37746 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37880 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38036 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38041 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38042 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38132 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38140 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38199 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38203 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38205 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38207 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38237 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38261 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38284 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38311 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38597 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38605 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38621 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39762 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39775 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39789 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39822 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39830 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39833 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39834 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39910 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39925 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39933 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68209 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68236 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68304 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68353 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68368 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68730 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71117 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71141 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71188 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23007 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23017 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23137 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23152 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23217 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23259 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23265 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23346 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23371 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23377 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23385 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31420 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31435 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31526 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31537 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31560 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31562 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31579 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31591 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31630 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31732 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43010 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43029 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43034 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43083 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43101 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43115 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43118 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2008-2544 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4915 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4916 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4917 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2014-9892 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2014-9900 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-10723 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-8660 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13693 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13694 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-12928 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12378 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12379 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12380 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12381 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12382 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12455 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31081 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31085 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40086 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68193 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68251 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68359 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW2.8 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 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.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW2.69 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW2.69 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | LOW2.65 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | LOW2.65 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.64 | jq 1.7.1-6+deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4563 | LOW2.55 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | LOW2.5 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.3% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2019-20794 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24864 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37906 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71074 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23348 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23394 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23469 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31456 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-0630 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-16230 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16234 | LOW2.4 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | login 1:4.16.0-2+really2.41-5 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-69720 | LOW2.39 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.39 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW2.35 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4010 | LOW2.35 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2012-4542 | LOW2.35 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW2.29 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW2.29 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW2.29 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68768 | LOW2.24 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW2.24 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2010-5321 | LOW2.19 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41848 | LOW2.14 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16089 | LOW2.09 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16229 | LOW2.09 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16231 | LOW2.09 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16232 | LOW2.09 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16233 | LOW2.09 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW1.81 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW1.73 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2015-2877 | LOW1.68 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68751 | LOW1.68 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-40113 | LOW1.27 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-11191 | LOW1.27 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.07 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-47770 | NONE0 | jq 1.7.1-6+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-47770 | NONE0 | libjq1 1.7.1-6+deb13u2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 No fix yet | — | 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-44893 | NONE0 | io.netty:netty-codec-haproxy 4.2.14.Final fixed in 4.2.15.Final, 4.1.135.Final | — | Not Applicable |
| CVE-2026-47244 | NONE0 | io.netty:netty-codec-http2 4.2.14.Final fixed in 4.2.15.Final, 4.1.135.Final | — | Not Applicable |
| CVE-2026-44249 | NONE0 | io.netty:netty-handler 4.2.14.Final fixed in 4.2.15.Final, 4.1.135.Final | — | Not Applicable |
| CVE-2026-45416 | NONE0 | io.netty:netty-handler 4.2.14.Final fixed in 4.2.15.Final, 4.1.135.Final | — | Not Applicable |
| CVE-2026-45536 | NONE0 | io.netty:netty-transport-native-epoll 4.2.14.Final fixed in 4.2.15.Final, 4.1.135.Final | — | Not Applicable |
| CVE-2026-45536 | NONE0 | io.netty:netty-transport-native-kqueue 4.2.14.Final fixed in 4.2.15.Final, 4.1.135.Final | — | Not Applicable |