This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could achieve arbitrary code execution within the container through vulnerabilities like CVE-2026-48962 in `libperl5.40`, potentially compromising the application or underlying host. With 404 exposed vulnerabilities, including 78 rated 6.0 or higher severity, the attack surface is substantial. While it is an Official Docker Hub image, the number and severity of critical findings necessitate immediate remediation or selection of a more secure alternative.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-48962 | HIGH7.8 | libperl5.40 5.40.1-6 No fix yet | — | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | HIGH7.48 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM6.88 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| 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-2026-6846 | 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-2026-6846 | 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-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 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-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 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-6846 | MEDIUM6.63 | libsframe1 2.44-3 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.2% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-9192 | MEDIUM6.38 | libc6 2.41-12+deb13u3 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.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5773 | MEDIUM6.38 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6276 | MEDIUM6.38 | libcurl4t64 8.14.1-2+deb13u3 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.2% Theoretical Threat | Directly Exposed |
| CVE-2020-36325 | MEDIUM6.38 | libjansson4 2.14-2+b3 No fix yet | 0.7% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM6.18 | libssh2-1t64 1.11.1-1 No fix yet | <0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| 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-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-2018-20796 | MEDIUM6 | libc-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-20796 | MEDIUM6 | libc6 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2015-3276 | MEDIUM6 | libldap2 2.6.10+dfsg-1 No fix yet | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-1965 | MEDIUM5.78 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14819 | MEDIUM5.78 | libcurl4t64 8.14.1-2+deb13u3 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-2018-20712 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3784 | MEDIUM5.52 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5545 | MEDIUM5.52 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6429 | MEDIUM5.52 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14524 | MEDIUM5.52 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | MEDIUM5.46 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | MEDIUM5.46 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-3805 | MEDIUM5.35 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 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 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-6951 | MEDIUM5.17 | patch 2.8-2 No fix yet | 15.3% High Exploitation Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM5.17 | patch 2.8-2 No fix yet | 11.8% High Exploitation Risk | Post-Exploit |
| CVE-2025-1153 | MEDIUM5.02 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 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 | libcurl4t64 8.14.1-2+deb13u3 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-2026-40355 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <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-2026-40355 | MEDIUM5.02 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libk5crypto3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <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-2026-40355 | MEDIUM5.02 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5-3 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <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-2026-40355 | MEDIUM5.02 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM5.02 | libkrb5support0 1.21.3-5 fixed in 1.21.3-5+deb13u1 | <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-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-2019-1010022 | MEDIUM5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | MEDIUM5 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | — | Directly Exposed |
| CVE-2026-3783 | MEDIUM4.84 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| 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-2013-7445 | MEDIUM4.68 | linux-libc-dev 6.12.88-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-46243 | MEDIUM4.68 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-2 | — | Post-Exploit |
| CVE-2026-46300 | MEDIUM4.68 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46274 | MEDIUM4.68 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-48962 | MEDIUM4.68 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| 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-2026-6844 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | <0.1% 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-2026-6844 | 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-2026-6844 | MEDIUM4.67 | libctf0 2.44-3 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-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | <0.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-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42497 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM4.5 | libc6 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010025 | MEDIUM4.5 | libc6 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-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-2026-4873 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6253 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7168 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u3 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-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-1010023 | MEDIUM4.49 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | MEDIUM4.49 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-46244 | MEDIUM4.38 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2011-3389 | MEDIUM4.3 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 3.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46209 | MEDIUM4.26 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2008-4609 | MEDIUM4.26 | linux-libc-dev 6.12.88-1 No fix yet | 1.9% Low-Moderate Risk | Post-Exploit |
| 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-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-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-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.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-2026-6845 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.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-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.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-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-2 | — | Post-Exploit |
| CVE-2026-43503 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-45932 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46054 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46117 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46181 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46227 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-45840 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45934 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46017 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46032 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46158 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46160 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46170 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46242 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46275 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2025-71313 | MEDIUM4.2 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | MEDIUM4.08 | libcurl4t64 8.14.1-2+deb13u3 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 | libcurl4t64 8.14.1-2+deb13u3 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 | libsmartcols1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-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-2026-6846 | 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-2026-6846 | 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-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-19449 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-19814 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-3847 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-21803 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58093 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38137 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38187 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38206 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38421 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39859 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39862 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39958 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23171 | LOW3.98 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23208 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31493 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31688 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12456 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-19378 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-11725 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-26934 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-25265 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3238 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-26242 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3640 | LOW3.98 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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.2% 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.2% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-9192 | LOW3.82 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-19070 | LOW3.82 | linux-libc-dev 6.12.88-1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2022-0400 | LOW3.82 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | LOW3.65 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% 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-2024-58015 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22104 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38204 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38636 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23102 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23327 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31568 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40064 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31613 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43414 | LOW3.62 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 3.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3864 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-31663 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43198 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40158 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40168 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43116 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43303 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-1247 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-2961 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-45884 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-45885 | LOW3.57 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | LOW3.57 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-1121 | LOW3.54 | linux-libc-dev 6.12.88-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-8376 | LOW3.53 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40130 | LOW3.47 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-36694 | LOW3.42 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6238 | LOW3.42 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW3.4 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.4 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.31 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-20712 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-6240 | LOW3.31 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68729 | LOW3.31 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-0564 | LOW3.31 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45836 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-45838 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45841 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45842 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45843 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45844 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45845 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45846 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45944 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46066 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46093 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46111 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46130 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46137 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46159 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46191 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46207 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46214 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46234 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46252 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46312 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2025-71315 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45897 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45901 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45961 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-45963 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46014 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46059 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46071 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46092 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46153 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46201 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46203 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46216 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46235 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-46256 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46279 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46302 | LOW3.3 | linux-libc-dev 6.12.88-1 No fix yet | — | Post-Exploit |
| CVE-2026-46313 | LOW3.3 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-40074 | LOW3.26 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44032 | LOW3.26 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-44033 | LOW3.26 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-3397 | LOW3.21 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40146 | LOW3.16 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 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-2025-1152 | LOW3.15 | libgprofng0 2.44-3 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-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-40355 | LOW3.11 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68319 | LOW3.11 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43197 | LOW3.11 | linux-libc-dev 6.12.88-1 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-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-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-3714 | LOW3.01 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | LOW3 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW3 | bzip2 1.0.8-6 No fix yet | — | Post-Exploit |
| CVE-2004-0230 | LOW3 | linux-libc-dev 6.12.88-1 No fix yet | 9.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-23039 | LOW2.91 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| 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-2026-6844 | 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-2026-6844 | 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-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31082 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-37454 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-2193 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-25740 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-52560 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56709 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58074 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58094 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58095 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21752 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21807 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-21949 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22108 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22109 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-22127 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23131 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23132 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-23135 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37743 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37746 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37880 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38029 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38036 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38041 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38042 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38064 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38132 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38140 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38199 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38203 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38205 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38207 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38237 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38261 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38284 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38311 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38359 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38597 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38605 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-38621 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39677 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39762 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39775 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39789 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39822 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39830 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39833 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39834 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39910 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39925 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-39933 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40102 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68209 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68236 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68304 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68353 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68368 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68730 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71117 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71141 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71188 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71202 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71227 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71285 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71289 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71302 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23007 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23017 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23137 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23152 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23217 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23247 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23259 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23265 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23272 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23346 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23371 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23377 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23385 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23472 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31420 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31435 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31526 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31537 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31560 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31562 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31579 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31591 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31592 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31630 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31692 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31732 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31771 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31777 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43009 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43010 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43022 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43029 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43034 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43042 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43048 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43083 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43101 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43115 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43118 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43127 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43172 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43191 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43204 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43213 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43216 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43219 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43234 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43272 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43294 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43298 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43299 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43301 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43308 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43309 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43310 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43311 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43325 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43326 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43331 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43337 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43344 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43346 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43352 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43353 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43355 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43416 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43443 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43463 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43464 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43465 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2008-2544 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4915 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4916 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-4917 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2014-9892 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2014-9900 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-10723 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2016-8660 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13693 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13694 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-12928 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12378 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12379 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12380 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12381 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12382 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-12455 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-4543 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31081 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-31085 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40086 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68193 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68251 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68359 | LOW2.8 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31486 | LOW2.8 | linux-libc-dev 6.12.88-1 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-2018-21232 | LOW2.8 | re2c 4.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% 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-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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% 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-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.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% 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-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.7 | libgssapi-krb5-2 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libk5crypto3 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5-3 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libkrb5support0 1.21.3-5 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW2.7 | libldap2 2.6.10+dfsg-1 No fix yet | 6.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | LOW2.7 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| 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-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW2.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2019-1010025 | LOW2.7 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40217 | LOW2.65 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40338 | LOW2.65 | linux-libc-dev 6.12.88-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-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-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-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.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-2026-6845 | LOW2.55 | binutils-common 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.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-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc-dev-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc6-dev 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4563 | LOW2.55 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | LOW2.5 | linux-libc-dev 6.12.88-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.3% 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-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-20794 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-24864 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-37906 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-40139 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68745 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-71074 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23348 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23394 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-23469 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-31456 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43053 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-0630 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-16230 | LOW2.4 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16234 | LOW2.4 | linux-libc-dev 6.12.88-1 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-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-2019-15213 | LOW2.35 | linux-libc-dev 6.12.88-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-4010 | LOW2.35 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2012-4542 | LOW2.35 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW2.29 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW2.24 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68768 | LOW2.24 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2018-17977 | LOW2.24 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2010-5321 | LOW2.19 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW2.16 | passwd 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41848 | LOW2.14 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16089 | LOW2.09 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16229 | LOW2.09 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16231 | LOW2.09 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16232 | LOW2.09 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-16233 | LOW2.09 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2010-4756 | LOW2.04 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-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-2020-35501 | LOW1.73 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% 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.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% 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-2015-2877 | LOW1.68 | linux-libc-dev 6.12.88-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68751 | LOW1.68 | linux-libc-dev 6.12.88-1 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-2026-2903 | LOW1.68 | re2c 4.1-1 No fix yet | <0.1% 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-40113 | LOW1.27 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-11191 | LOW1.27 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.07 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| 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-2025-14104 | NONE0 | liblastlog2-2 2.41-5 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-2026-3184 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | liblastlog2-2 2.41-5 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 4.5% Low-Moderate Risk | 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 |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | libssl3t64 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46211 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46220 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46231 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46232 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46233 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46236 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.12.88-1 fixed in 6.12.90-1 | — | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.88-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34180 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34181 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34182 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34183 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42764 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42766 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42767 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42768 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42769 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-42770 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45445 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45446 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-45447 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7383 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-9076 | NONE0 | openssl-provider-legacy 3.5.6-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |