Last scanned:
This base/runtime image ships critical vulnerabilities that any image built on it would inherit; they must be remediated before the final image goes to production. An attacker could achieve remote code execution or cause denial of service by sending malicious XML or regex patterns. Remediation requires updating libxml2 and glibc packages to patched versions. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH8.33 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.12.95-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.12.95-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38137 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38187 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38421 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39862 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39958 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46279 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.12.95-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libsframe1 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.12.95-1 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libsframe1 2.44-3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58015 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23102 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2015-3276 | MEDIUM6 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53000 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53277 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53281 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46317 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46325 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52953 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53005 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53250 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53260 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.12.95-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.12.95-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40130 | MEDIUM5.78 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-6238 | MEDIUM5.7 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.12.95-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-68729 | MEDIUM5.52 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.12.95-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libsframe1 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.12.95-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53365 | MEDIUM5.5 | linux-libc-dev 6.12.95-1 No fix yet | — | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45932 | MEDIUM5.44 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53092 | MEDIUM5.44 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68319 | MEDIUM5.18 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43197 | MEDIUM5.18 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.12.95-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.12.95-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56709 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58074 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21752 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21807 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22108 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23135 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37743 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37746 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38036 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38199 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38205 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38284 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38605 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38621 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39775 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39822 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39830 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39834 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68353 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68368 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68730 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71117 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71141 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71302 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23007 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23017 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23152 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23217 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23259 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23377 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23385 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31435 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31526 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31562 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31591 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43029 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43034 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43127 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43191 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43272 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43294 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43298 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43301 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43311 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43325 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43326 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43337 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43346 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43463 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43464 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43465 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43485 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46066 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46093 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46096 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46171 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46228 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46256 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46314 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52944 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52994 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53027 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53103 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53109 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53118 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53226 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53285 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53297 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53313 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53321 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40086 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68193 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68359 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53102 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53104 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53106 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53113 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-40217 | MEDIUM4.42 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | liblastlog2-2 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37906 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46272 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.12.95-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | curl 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-68360 | LOW3.82 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.12.95-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | LOW3.31 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | libperl5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-base 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-modules-5.40 5.40.1-6 No fix yet | — | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2008-4609 | LOW2.94 | linux-libc-dev 6.12.95-1 No fix yet | 32.1% High Exploitation Risk | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2013-7445 | LOW2.81 | linux-libc-dev 6.12.95-1 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19449 | LOW2.81 | linux-libc-dev 6.12.95-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19814 | LOW2.81 | linux-libc-dev 6.12.95-1 No fix yet | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-19378 | LOW2.81 | linux-libc-dev 6.12.95-1 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25265 | LOW2.81 | linux-libc-dev 6.12.95-1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-56288 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.8-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.12.95-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-68751 | LOW2.8 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.44-3 No fix yet | 0.6% 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.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 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.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-40113 | LOW2.12 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.12.95-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-21232 | NONE0 | re2c 4.1-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2903 | NONE0 | re2c 4.1-1 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-53615 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-58055 | NONE0 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.95-1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 No fix yet | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.