Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could remotely exploit the HTTP/2 denial-of-service vulnerability (CVE-2026-49975) to crash Apache, or the libxml2 use-after-free (CVE-2026-6653) to execute arbitrary code, and the OpenSSL flaw (CVE-2026-45445) may lead to data confidentiality loss if the application uses the affected API. Disabling HTTP/2 in Apache fully mitigates CVE-2026-49975. Note that CVE-2026-45445 only applies if Drupal uses the EVP_Cipher() one-shot interface, which is uncommon.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-49975 | HIGH8.62 | apache2 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | 11.5% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-49975 | HIGH8.62 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | 11.5% High Exploitation Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-45445 | HIGH7.73 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| 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 | 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-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-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% 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-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-2026-25210 | MEDIUM6.63 | libexpat1 2.7.1-2 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+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44631 | MEDIUM6.54 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44631 | MEDIUM6.54 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% 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-2026-34355 | MEDIUM6.38 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42536 | MEDIUM6.38 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34356 | MEDIUM6.38 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34355 | MEDIUM6.38 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42536 | MEDIUM6.38 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34356 | MEDIUM6.38 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | 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-2026-45186 | MEDIUM6.38 | libexpat1 2.7.1-2 No fix yet | 0.4% 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-34183 | MEDIUM6.38 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34183 | MEDIUM6.38 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2007-0086 | MEDIUM6.24 | apache2 2.4.67-1~deb13u2 No fix yet | 9.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2007-0086 | MEDIUM6.24 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 9.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-44185 | MEDIUM6.21 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44186 | MEDIUM6.21 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48913 | MEDIUM6.21 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | MEDIUM6.21 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-44186 | MEDIUM6.21 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48913 | MEDIUM6.21 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 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-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-2025-13151 | MEDIUM5.9 | libtasn1-6 4.20.0-2 fixed in 4.20.0-2+deb13u1 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | MEDIUM5.88 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | MEDIUM5.88 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-42535 | MEDIUM5.52 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43951 | MEDIUM5.52 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42535 | MEDIUM5.52 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43951 | MEDIUM5.52 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | 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 | libc6 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-2025-15649 | MEDIUM5.52 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% 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-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% 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 | 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-2025-59375 | MEDIUM5.3 | libexpat1 2.7.1-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45440 | MEDIUM5.3 | drupal/core 9.8.0 fixed in 10.3.6, 11.0.5, 10.2.9 | 9.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45440 | MEDIUM5.3 | drupal/core-recommended 9.8.0 fixed in 10.3.6, 11.0.5, 10.2.9 | 9.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-2026-1757 | MEDIUM5.27 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 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-2026-5435 | MEDIUM5.02 | libc-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-50219 | MEDIUM5.02 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.7.1-2 No fix yet | 0.1% 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-2026-42764 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% 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-2026-44119 | MEDIUM4.67 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44119 | MEDIUM4.67 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.2% Theoretical Threat | 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-66382 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-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-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.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-7598 | MEDIUM4.64 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | MEDIUM4.64 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| 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-29170 | MEDIUM4.59 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29170 | MEDIUM4.59 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u3 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-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% 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-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48998 | MEDIUM4.5 | guzzlehttp/psr7 2.8.1 fixed in 2.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2 2.4.67-1~deb13u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2 2.4.67-1~deb13u2 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 3.7% Low-Moderate Risk | 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 | 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-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-2026-34180 | MEDIUM4.25 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2 2.4.67-1~deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u3 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-2010-4756 | MEDIUM4 | libc-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-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-2025-69720 | LOW3.98 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% 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-44631 | LOW3.93 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-29167 | LOW3.91 | apache2 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-29167 | LOW3.91 | apache2-bin 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% 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+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34355 | LOW3.82 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42536 | LOW3.82 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34356 | LOW3.82 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | 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+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u3 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+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34183 | LOW3.82 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% 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-9547 | LOW3.77 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW3.74 | apache2 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44185 | LOW3.72 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-44186 | LOW3.72 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48913 | LOW3.72 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u3 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-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-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-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42535 | LOW3.31 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-43951 | LOW3.31 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| 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-3784 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1t64 1.11.1-1 fixed in 1.11.1-1+deb13u1 | 0.3% 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-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-2026-3805 | LOW3.21 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3805 | LOW3.21 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 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-2026-41080 | LOW3.15 | libexpat1 2.7.1-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% 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 | login 1:4.16.0-2+really2.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-49975 | LOW3.1 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | 11.5% High Exploitation Risk | 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+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42764 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% 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-0456 | LOW2.99 | apache2 2.4.67-1~deb13u2 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.99 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-provider-legacy 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| 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-2007-0086 | LOW2.81 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 9.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-44119 | LOW2.8 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.2% Theoretical Threat | 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 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.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-2025-8732 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% 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-2026-45445 | LOW2.78 | libssl3t64 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-29170 | LOW2.75 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% 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-4873 | LOW2.7 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4t64 8.14.1-2+deb13u3 fixed in 8.14.1-2+deb13u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.3% 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-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-2026-34743 | LOW2.7 | xz-utils 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 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-2003-1581 | LOW2.6 | apache2 2.4.67-1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | LOW2.58 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2003-1580 | LOW2.58 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-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-34180 | LOW2.55 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% 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-2007-3303 | LOW2.5 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 0.9% 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-0992 | LOW2.46 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u2 fixed in 2.12.7+dfsg+really2.9.14-2.1+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u3 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+deb13u3 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.44-3 No fix yet | 0.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-2026-29167 | LOW2.35 | apache2-utils 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW2.24 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| 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-2026-24515 | LOW2.12 | libexpat1 2.7.1-2 No fix yet | 0.2% 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-2026-45446 | LOW1.89 | openssl 3.5.6-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% 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-2008-0456 | LOW1.79 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 19.0% High Exploitation Risk | Post-Exploit |
| CVE-2001-1534 | LOW1.78 | apache2 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-bin 2.4.67-1~deb13u2 No fix yet | 0.7% 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-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 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-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-2003-1581 | LOW1.56 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | 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-2001-1534 | LOW1.07 | apache2-utils 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-10263 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-0086 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 9.6% Low-Moderate Risk | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-22069 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46323 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52943 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52962 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52969 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52992 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53004 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53136 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53137 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53148 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53157 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53195 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53233 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53234 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53294 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53296 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53359 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53362 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44631 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34355 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42536 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-49975 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.67-1~deb13u3 | 11.5% High Exploitation Risk | Not Applicable |
| CVE-2026-34356 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-53266 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53071 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-44185 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44186 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-48913 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46244 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46203 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52968 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53138 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53149 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53255 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53303 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53309 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31613 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46117 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46242 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46316 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52951 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52976 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52989 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52993 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53002 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53006 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53202 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53203 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53360 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43116 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43303 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46275 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46319 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52912 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52917 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52918 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52920 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52924 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-52935 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52942 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52947 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52957 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52986 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52998 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53011 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53016 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53031 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53036 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53049 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53062 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53072 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53073 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53075 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53110 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53131 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53133 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53182 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53189 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53192 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53193 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53209 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53212 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53223 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53228 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53235 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53239 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53242 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53253 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53254 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53256 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53260 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53264 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53268 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53270 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53275 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53341 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53354 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53355 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53357 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53366 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | — | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53196 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46331 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53094 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-42535 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43951 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53176 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53033 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53074 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53081 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53085 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53092 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53059 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43197 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-52908 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52923 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44119 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21807 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23131 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23272 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31732 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43219 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43331 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43355 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45838 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45840 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45841 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45842 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45843 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-45844 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45845 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45846 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46093 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46137 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46160 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46216 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46252 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46315 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46320 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46321 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46322 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52913 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52915 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52916 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52921 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52925 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52926 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52927 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52929 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52930 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52939 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52941 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52946 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-52948 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52954 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52958 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52963 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52964 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52967 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52970 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52972 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52975 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52977 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52980 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52981 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52982 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-52984 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52985 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52995 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52996 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52999 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53001 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53003 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53012 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53013 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53014 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53021 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53022 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53023 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53032 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53034 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53035 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53037 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53038 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53039 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53047 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53050 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53052 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53061 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53069 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53077 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53084 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53086 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53096 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53101 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53105 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53128 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53134 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53135 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53139 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53140 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53142 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53144 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53146 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53147 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53150 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53151 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53152 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53154 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53158 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53159 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53163 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53167 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53168 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53177 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53180 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53181 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53183 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53184 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53190 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53191 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53199 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53205 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53207 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53208 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53210 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53213 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53214 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53218 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53219 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53221 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53225 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53227 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53236 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53238 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53241 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53245 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53249 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53251 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53252 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53261 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53263 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53269 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53271 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53274 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53279 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53287 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53288 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53289 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53291 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53293 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53295 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53298 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53304 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53306 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53314 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53318 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53320 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53325 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53349 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53365 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | — | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68251 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52974 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53048 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53051 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53058 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53060 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53063 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53064 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53080 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53088 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53093 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53111 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53123 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53126 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53327 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.95-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53337 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53339 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53347 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53350 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53352 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-21232 | NONE0 | re2c 4.1-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-29170 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% 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-53194 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 80.9% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2007-3303 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.90-2 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-2019-20794 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23469 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52955 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-29167 | NONE0 | apache2-data 2.4.67-1~deb13u2 fixed in 2.4.68-1~deb13u1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-1743 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2003-1307 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2003-1580 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 3.7% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-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-2015-2877 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-2903 | NONE0 | re2c 4.1-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2003-1581 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2008-0456 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 19.0% High Exploitation Risk | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2001-1534 | NONE0 | apache2-data 2.4.67-1~deb13u2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.3% 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+deb13u3 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+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.7.1-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.7.1-2 No fix yet | <0.1% 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.90-2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52911 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53046 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53198 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40098 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31717 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43245 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53056 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53066 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53328 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.90-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53331 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53336 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53343 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53346 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53065 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53082 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53097 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53098 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53112 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53119 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53160 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53247 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 6.12.90-2 fixed in 6.12.94-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.90-2 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 |
| CVE-2026-55568 | NONE0 | guzzlehttp/guzzle 7.10.5 fixed in 7.12.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55767 | NONE0 | guzzlehttp/guzzle 7.10.5 fixed in 7.12.1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-49214 | NONE0 | guzzlehttp/psr7 2.8.1 fixed in 2.10.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-55766 | NONE0 | guzzlehttp/psr7 2.8.1 fixed in 2.12.1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-9082 | NONE0 | drupal/core 9.8.0 fixed in 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, 11.3.10 | 84.6% Actively Exploited | Not Applicable |
| CVE-2024-55637 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-55638 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 7.102 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-12393 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55634 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-13081 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-3057 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31673 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-31674 | NONE0 | drupal/core 9.8.0 fixed in 10.3.13, 10.4.3, 11.0.12, 11.1.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-6365 | NONE0 | drupal/core 9.8.0 fixed in 10.5.9, 10.6.7, 11.2.11, 11.3.7 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6366 | NONE0 | drupal/core 9.8.0 fixed in 10.5.9, 10.6.7, 11.2.11, 11.3.7 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-6ccv-8fgf-cjpw | NONE0 | drupal/core 9.8.0 fixed in 10.1.8, 10.2.2 | — | Not Applicable |
| CVE-2024-55636 | NONE0 | drupal/core 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-13080 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-13082 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-13083 | NONE0 | drupal/core 9.8.0 fixed in 10.4.9, 10.5.6, 11.1.9, 11.2.8, 7.103 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-31675 | NONE0 | drupal/core 9.8.0 fixed in 10.3.14, 10.4.5, 11.0.13, 11.1.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-55637 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-55638 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 7.102 | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-12393 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-55634 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-55636 | NONE0 | drupal/core-recommended 9.8.0 fixed in 10.2.11, 10.3.9, 11.0.8 | 0.9% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.