This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve remote code execution and full compromise of the container by exploiting vulnerabilities such as CVE-2026-40393 (via crafted web content using Playwright) or CVE-2026-33228 (via crafted JSON input). The image also contains a high volume of other exposed critical vulnerabilities, with 31 having a severity of 7.0 or higher. Note that CVE-2026-4800 for Lodash only applies if the application passes untrusted input as key names in `options.imports` to `_.template`.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-40393 | CRITICAL9.8 | libgbm1 25.0.7-2 No fix yet | — | Directly ExposedContext importance: HIGH |
| CVE-2026-40393 | CRITICAL9.8 | libgl1-mesa-dri 25.0.7-2 No fix yet | — | Directly ExposedContext importance: HIGH |
| CVE-2026-40393 | CRITICAL9.8 | libglx-mesa0 25.0.7-2 No fix yet | — | Directly ExposedContext importance: HIGH |
| CVE-2026-40393 | CRITICAL9.8 | mesa-libgallium 25.0.7-2 No fix yet | — | Directly ExposedContext importance: HIGH |
| CVE-2026-33228 | HIGH8.33 | node-flatted 3.2.7~ds-1 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-4800 | HIGH8.33 | node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-4800 | HIGH8.33 | node-lodash-packages 4.17.21+dfsg+~cs8.31.198.20210220-9 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-6100 | HIGH8.1 | libpython3.13-dev 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-6100 | HIGH8.1 | libpython3.13-minimal 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-6100 | HIGH8.1 | libpython3.13-stdlib 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-6100 | HIGH8.1 | python3.13 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-6100 | HIGH8.1 | python3.13-dev 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-6100 | HIGH8.1 | python3.13-minimal 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u2 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 6.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3+deb13u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-bin 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2016-9580 | HIGH7.48 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9581 | HIGH7.48 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-16376 | HIGH7.48 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2008-4609 | HIGH7.1 | linux-libc-dev 6.12.74-2 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31419 | HIGH7 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-33941 | MEDIUM6.97 | handlebars 3:4.7.7+~4.1.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33938 | MEDIUM6.88 | handlebars 3:4.7.7+~4.1.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33940 | MEDIUM6.88 | handlebars 3:4.7.7+~4.1.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23401 | MEDIUM6.88 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34873 | MEDIUM6.8 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4878 | MEDIUM6.7 | libcap2 1:2.75-10+b8 No fix yet | — | Directly Exposed |
| CVE-2026-33937 | MEDIUM6.66 | handlebars 3:4.7.7+~4.1.0-1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-34875 | MEDIUM6.66 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-1525 | MEDIUM6.66 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-7445 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-19449 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-19814 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38627 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23231 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19378 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-25265 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | ffmpeg 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libavcodec61 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libavdevice61 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libavfilter10 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libavformat61 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libavutil59 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libpostproc58 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libswresample5 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6385 | MEDIUM6.5 | libswscale8 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.48 | libpython3.13 3.13.5-2 No fix yet | — | Directly ExposedContext importance: MEDIUM |
| CVE-2026-40225 | MEDIUM6.4 | libsystemd0 257.9-1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-40226 | MEDIUM6.4 | libsystemd0 257.9-1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-40225 | MEDIUM6.4 | libudev1 257.9-1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-40226 | MEDIUM6.4 | libudev1 257.9-1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-33939 | MEDIUM6.38 | handlebars 3:4.7.7+~4.1.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-bin 2.41-12+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6 2.41-12+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.192-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-36325 | MEDIUM6.38 | libjansson4 2.14-2+b3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-27601 | MEDIUM6.38 | libjs-underscore 1.13.4~dfsg+~1.11.4-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1837 | MEDIUM6.38 | libjxl0.11 0.11.1-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-36691 | MEDIUM6.38 | libjxl0.11 0.11.1-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34872 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-1000520 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-43615 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.64.0-1.1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-9113 | MEDIUM6.38 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9114 | MEDIUM6.38 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | libpython3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | libpython3.13-dev 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-dev 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-19070 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2022-0400 | MEDIUM6.38 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69873 | MEDIUM6.38 | node-ajv 8.12.0~ds+~2.1.1-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24001 | MEDIUM6.38 | node-diff 5.0.0~dfsg+~5.0.1-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32141 | MEDIUM6.38 | node-flatted 3.2.7~ds-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-26996 | MEDIUM6.38 | node-minimatch 9.0.3-6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34043 | MEDIUM6.38 | node-serialize-javascript 6.0.2-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1526 | MEDIUM6.38 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1528 | MEDIUM6.38 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22036 | MEDIUM6.38 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2229 | MEDIUM6.38 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | python3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | python3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | python3.13-dev 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | python3.13-dev 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13836 | MEDIUM6.38 | python3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | python3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM6.03 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-26960 | MEDIUM6.03 | node-tar 6.2.1+~cs7.0.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23270 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23375 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-5574 | MEDIUM5.95 | xserver-common 2:21.1.16-1.3+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-5574 | MEDIUM5.95 | xvfb 2:21.1.16-1.3+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | ffmpeg 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libavcodec61 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libavdevice61 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libavfilter10 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libavformat61 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libavutil59 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libpostproc58 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libswresample5 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-30997 | MEDIUM5.9 | libswscale8 7:7.1.3-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.74-2 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31414 | MEDIUM5.8 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31426 | MEDIUM5.8 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31427 | MEDIUM5.8 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2025-13034 | MEDIUM5.78 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | MEDIUM5.78 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM5.7 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM5.61 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM5.61 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM5.61 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM5.52 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-18064 | MEDIUM5.52 | libcairo2 1.18.4-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf0 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libgprofng0 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.2% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | MEDIUM5.52 | libjbig0 2.1-6.1+b2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25834 | MEDIUM5.52 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-10505 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2016-9115 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-9116 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2016-9117 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-6988 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libsframe1 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM5.52 | libssh-4 0.11.2-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-10126 | MEDIUM5.52 | libtiff6 4.7.0-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-1210 | MEDIUM5.52 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33671 | MEDIUM5.52 | node-anymatch 3.1.3+~cs4.6.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25547 | MEDIUM5.52 | node-brace-expansion 2.0.1+~1.1.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33750 | MEDIUM5.52 | node-brace-expansion 2.0.1+~1.1.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27904 | MEDIUM5.52 | node-minimatch 9.0.3-6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23167 | MEDIUM5.52 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1527 | MEDIUM5.52 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31416 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31421 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31423 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31424 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31425 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2026-31428 | MEDIUM5.5 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23319 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23450 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3805 | MEDIUM5.35 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | MEDIUM5.35 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29786 | MEDIUM5.35 | node-tar 6.2.1+~cs7.0.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.13 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.13-dev 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.13-minimal 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | libpython3.13-stdlib 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | python3.13 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | python3.13-dev 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-3446 | MEDIUM5.3 | python3.13-minimal 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40147 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM5.27 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 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-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 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-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23745 | MEDIUM5.18 | node-tar 6.2.1+~cs7.0.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | MEDIUM5.02 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libk5crypto3 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5-3 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.02 | libkrb5support0 1.21.3-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66442 | MEDIUM5.02 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.02 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.02 | libtasn1-6 4.20.0-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23246 | MEDIUM5.02 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.02 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27903 | MEDIUM5.02 | node-minimatch 9.0.3-6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23950 | MEDIUM5.02 | node-tar 6.2.1+~cs7.0.8-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2581 | MEDIUM5.02 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM5.02 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2004-0230 | MEDIUM5 | linux-libc-dev 6.12.74-2 No fix yet | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23317 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3783 | MEDIUM4.84 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | MEDIUM4.8 | tar 1.35+dfsg-3.1 No fix yet | 3.3% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2025-1178 | 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM4.76 | libtheoradec1 1.2.0~alpha1+dfsg-6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM4.76 | libtheoraenc1 1.2.0~alpha1+dfsg-6 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.7 | linux-libc-dev 6.12.74-2 No fix yet | — | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | 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.1% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM4.67 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM4.67 | libcairo2 1.18.4-1+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-20673 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-9996 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-4 0.11.2-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u2 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-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-14027 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-2193 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21709 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22116 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22117 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68251 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22981 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22985 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22993 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23070 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23104 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23244 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23249 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23250 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23251 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23252 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23297 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23306 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23313 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23316 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23343 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23359 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23360 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23363 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23369 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23386 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23412 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23413 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23414 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23417 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23441 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23445 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23454 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23461 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23466 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23473 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23475 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31394 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31406 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | python3.13-minimal 3.13.5-2 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-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | libpython3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | libpython3.13-dev 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | python3.13-dev 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM4.59 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.41-12+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.41-12+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.41-12+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.41-12+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM4.5 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59375 | MEDIUM4.5 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 10.2.0-1+b1 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-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33672 | MEDIUM4.5 | node-anymatch 3.1.3+~cs4.6.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-64718 | MEDIUM4.5 | node-js-yaml 4.1.0+dfsg+~4.0.5-7 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | MEDIUM4.5 | node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13465 | MEDIUM4.5 | node-lodash-packages 4.17.21+dfsg+~cs8.31.198.20210220-9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2950 | MEDIUM4.5 | node-lodash-packages 4.17.21+dfsg+~cs8.31.198.20210220-9 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | libpython3.13 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | libpython3.13-dev 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3.13 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3.13-dev 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2026-1502 | MEDIUM4.5 | python3.13-minimal 3.13.5-2 No fix yet | — | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | MEDIUM4.49 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | MEDIUM4.4 | libpng16-16t64 1.6.48-1+deb13u4 No fix yet | — | Directly Exposed |
| CVE-2024-45157 | MEDIUM4.33 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71239 | MEDIUM4.33 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30t64 3.8.9-3+deb13u2 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM4.25 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM4.25 | libssh-4 0.11.2-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM4.25 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14017 | MEDIUM4.08 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-dev 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3.13 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3.13-dev 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | python3.13-minimal 3.13.5-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33916 | MEDIUM4 | handlebars 3:4.7.7+~4.1.0-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-15224 | MEDIUM4 | libcurl3t64-gnutls 8.14.1-2+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 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 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22986 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23210 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23440 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31389 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.74-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-24975 | LOW3.82 | git 1:2.47.3-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW3.82 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-dev 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3.13-dev 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69277 | LOW3.82 | PyNaCl 1.5.0 fixed in 1.6.2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23370 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31401 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-dev 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-dev 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.13-stdlib 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.65 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3.13 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3.13 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3.13-dev 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3.13-dev 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | python3.13-minimal 3.13.5-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | python3.13-minimal 3.13.5-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW3.6 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 1.5% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2026-0775 | LOW3.57 | npm 9.2.0~ds1-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | LOW3.57 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6-dev 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.31 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-x86-64-linux-gnu 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.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4437 | LOW3.31 | libc-dev-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6192 | LOW3.3 | libopenjp2-7 2.5.3-2.1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.15 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.15 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.15 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 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-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-2018-6951 | LOW3.1 | patch 2.8-2 No fix yet | 15.3% High Exploitation Risk | Post-Exploit |
| CVE-2018-6952 | LOW3.1 | patch 2.8-2 No fix yet | 11.8% High Exploitation Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1153 | LOW3.01 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-bin 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6-dev 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW2.9 | libsystemd0 257.9-1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-40228 | LOW2.9 | libudev1 257.9-1~deb13u1 No fix yet | — | Directly Exposed |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 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.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-20673 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-9996 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | 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.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-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.2% 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-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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.18.4-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.18.4-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 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-2026-0965 | LOW2.8 | libssh-4 0.11.2-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23321 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23335 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23354 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23380 | LOW2.8 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59436 | LOW2.72 | node-ip 2.0.1+~1.1.3-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc-dev-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12474 | LOW2.63 | libjxl0.11 0.11.1-4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-4 0.11.2-1+deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-47279 | LOW2.63 | node-undici 7.3.0+dfsg1+~cs24.12.11-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW2.55 | git 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.55 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| 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-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-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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1485 | LOW2.38 | libglib2.0-0t64 2.84.4-3~deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | 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.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-24515 | LOW2.12 | libexpat1-dev 2.7.1-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | libpython3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | libpython3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | libpython3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | libpython3.13-stdlib 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | python3.13 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | python3.13-dev 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.12 | python3.13-minimal 3.13.5-2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW2.04 | libc-dev-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc-dev-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.89 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.89 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.89 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.89 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68157 | LOW1.89 | webpack 5.97.1+dfsg1+~cs11.18.27-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68458 | LOW1.89 | webpack 5.97.1+dfsg1+~cs11.18.27-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.2% 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-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.44-3 No fix yet | <0.1% 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.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.24.6 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2014-8166 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-36600 | NONE0 | libcdio19t64 2.2.0-4 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61915 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0856 | NONE0 | libcaca0 0.99.beta20-5 No fix yet | 3.9% Low-Moderate Risk | Not Applicable |
| CVE-2026-34978 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50613 | NONE0 | libsndfile1 1.2.2-2+deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27447 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34980 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39314 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-39316 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58436 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-15853 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-15859 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-15861 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-15863 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34979 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.6 fixed in 1.24.9, 1.25.3 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34990 | NONE0 | libcups2t64 2.4.10-3+deb13u2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2-data 1.2.14-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2t64 1.2.14-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libsmartcols1 2.41-5 No fix yet | <0.1% 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 |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | <0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b8 No fix yet | — | Not Applicable |
| CVE-2025-22921 | NONE0 | ffmpeg 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavcodec61 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavdevice61 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavfilter10 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavformat61 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavutil59 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 25.0.7-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl1 1.7.0-1+b2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgl1-mesa-dri 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 25.0.7-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.7.0-1+b2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 25.0.7-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx0 1.7.0-1+b2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-25833 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-25835 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34871 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34874 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34876 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34877 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libpostproc58 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45927 | NONE0 | libslang2 2.3.3-5+b2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45929 | NONE0 | libslang2 2.3.3-5+b2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswresample5 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswscale8 7:7.1.3-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-25467 | NONE0 | libx264-164 2:0.164.3108+git31e19f9-2+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40150 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68175 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71265 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71266 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71267 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23279 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23281 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23284 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23285 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23291 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23308 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23324 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23325 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23334 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23339 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23347 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23356 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23364 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23373 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23378 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23387 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23396 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23422 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23426 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23427 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23428 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23438 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23446 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23460 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23464 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23468 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23470 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23474 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31391 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31409 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31412 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | — | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | — | Not Applicable |
| CVE-2026-31418 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | — | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.74-2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2023-45913 | NONE0 | mesa-libgallium 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | mesa-libgallium 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | mesa-libgallium 25.0.7-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | mesa-libgallium 25.0.7-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-59437 | NONE0 | node-ip 2.0.1+~1.1.3-3 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 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-33999 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34000 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34001 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34002 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34003 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-33999 | NONE0 | xvfb 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34000 | NONE0 | xvfb 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34001 | NONE0 | xvfb 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34002 | NONE0 | xvfb 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34003 | NONE0 | xvfb 2:21.1.16-1.3+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | <0.1% Theoretical Threat | Not Applicable |
| GHSA-cq8v-f236-94qc | NONE0 | rand 0.8.5 fixed in 0.9.3, 0.10.1 | — | Not Applicable |
| GHSA-cq8v-f236-94qc | NONE0 | rand 0.9.2 fixed in 0.9.3, 0.10.1 | — | Not Applicable |