Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit exposed components in this Drupal/Apache image to cause denial of service or, after gaining local access, escalate privileges via issues such as CVE-2026-16742, while CVE-2007-0086 is a disputed Apache Range-header DoS that requires an uncommon large TCP window. The official Docker publisher and digest pinning are positive trust signals, but they do not eliminate the 663 exposed vulnerabilities or the 11 exposed findings at severity 7.0 or above. Note that CVE-2007-0086 only applies under a non-default large TCP window condition, and CVE-2026-16742 is specific to systemd-homed environments; not using systemd-homed would fully eliminate CVE-2026-16742.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.41-12+deb13u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | HIGH7.22 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-0086 | HIGH7.18 | apache2 2.4.68-1~deb13u1 No fix yet | 10.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2007-0086 | HIGH7.18 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 10.2% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-77214 | MEDIUM6.97 | libexpat1 2.8.3-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56154 | MEDIUM6.88 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63292 | MEDIUM6.88 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73636 | MEDIUM6.88 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56154 | MEDIUM6.88 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63292 | MEDIUM6.88 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73636 | MEDIUM6.88 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56154 | MEDIUM6.88 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63292 | MEDIUM6.88 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-73636 | MEDIUM6.88 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM6.71 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | MEDIUM6.66 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.44-3 No fix yet | 0.3% 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-18220 | 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-2026-76642 | MEDIUM6.63 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.44-3 No fix yet | 0.3% 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-18220 | 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.44-3 No fix yet | 0.3% 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-18220 | 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-76957 | MEDIUM6.63 | libexpat1 2.8.3-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.44-3 No fix yet | 0.3% 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-18220 | 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-76642 | MEDIUM6.63 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libsframe1 2.44-3 No fix yet | 0.3% 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-18220 | 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-76642 | MEDIUM6.63 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM6.63 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM6.63 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86138 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86139 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libasan8 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libatomic1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libcc1-0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgcc-14-dev 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libgomp1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libhwasan0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libitm1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | liblsan0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libquadmath0 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libstdc++-14-dev 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libtsan2 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM6.54 | libubsan1 14.2.0-19 No fix yet | 0.4% 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-46729 | MEDIUM6.38 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56153 | MEDIUM6.38 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63686 | MEDIUM6.38 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63718 | MEDIUM6.38 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46729 | MEDIUM6.38 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56153 | MEDIUM6.38 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63686 | MEDIUM6.38 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63718 | MEDIUM6.38 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46729 | MEDIUM6.38 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56153 | MEDIUM6.38 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63686 | MEDIUM6.38 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63718 | MEDIUM6.38 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% 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-66046 | MEDIUM6.38 | libexpat1 2.8.3-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-76956 | MEDIUM6.38 | libexpat1 2.8.3-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93990 | MEDIUM6.38 | libexpat1 2.8.3-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 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-9538 | MEDIUM6.38 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM6.38 | libsasl2-2 2.1.28+dfsg1-9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107161 | MEDIUM6.38 | libsasl2-modules-db 2.1.28+dfsg1-9 No fix yet | 0.3% 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-88647 | MEDIUM6.29 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | MEDIUM6.29 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86143 | MEDIUM6.21 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.2% 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-2026-57941 | MEDIUM5.95 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-57941 | MEDIUM5.95 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-57941 | MEDIUM5.95 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libasan8 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libatomic1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-bin 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc-dev-bin 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM5.95 | libc6-dev 2.41-12+deb13u4 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM5.95 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libcc1-0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc-14-dev 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libgomp1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libhwasan0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libitm1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | liblsan0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libquadmath0 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++-14-dev 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libtsan2 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM5.95 | libubsan1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM5.95 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.44-3 No fix yet | 1.4% 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.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM5.78 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90803 | MEDIUM5.78 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90801 | MEDIUM5.61 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90828 | MEDIUM5.61 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90829 | MEDIUM5.61 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90831 | MEDIUM5.61 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% 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-2026-107778 | MEDIUM5.52 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | MEDIUM5.52 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libsframe1 2.44-3 No fix yet | 0.7% 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-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u4 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.41-12+deb13u4 No fix yet | 2.5% 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.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-90804 | MEDIUM5.18 | libbinutils 2.44-3 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-90804 | 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-90804 | 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-2026-90804 | MEDIUM5.18 | libgprofng0 2.44-3 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-2026-90804 | MEDIUM5.18 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86137 | MEDIUM5.18 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.02 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102633 | MEDIUM5.02 | libexpat1 2.8.3-1~deb13u1 fixed in 2.9.0-1~deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-67693 | MEDIUM5.02 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | MEDIUM4.84 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-73637 | MEDIUM4.76 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73637 | MEDIUM4.76 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73637 | MEDIUM4.76 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59797 | MEDIUM4.67 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59797 | MEDIUM4.67 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59797 | MEDIUM4.67 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% 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-19548 | 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-2026-90830 | MEDIUM4.67 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.1% 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-19548 | 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-2026-90830 | MEDIUM4.67 | libctf-nobfd0 2.44-3 No fix yet | 0.2% 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-19548 | 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-2026-90830 | MEDIUM4.67 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM4.67 | libfreetype6 2.13.3+dfsg-1+deb13u1 No fix yet | 0.2% 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-19548 | 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-2026-90830 | MEDIUM4.67 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u6 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-19548 | 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-2026-90830 | MEDIUM4.67 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-0 3.46.1-7+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.67 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% 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-93546 | MEDIUM4.59 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93546 | MEDIUM4.59 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93546 | MEDIUM4.59 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58415 | MEDIUM4.5 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63045 | MEDIUM4.5 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-79768 | MEDIUM4.5 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58415 | MEDIUM4.5 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63045 | MEDIUM4.5 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-79768 | MEDIUM4.5 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58415 | MEDIUM4.5 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63045 | MEDIUM4.5 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-79768 | MEDIUM4.5 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM4.5 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.3% 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-3184 | MEDIUM4.5 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2 2.4.68-1~deb13u1 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | MEDIUM4.3 | apache2-data 2.4.68-1~deb13u1 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1580 | MEDIUM4.3 | apache2-data 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u2 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-90802 | MEDIUM4.25 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.2% 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-2026-90802 | MEDIUM4.25 | libctf-nobfd0 2.44-3 No fix yet | 0.2% 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-2026-90802 | MEDIUM4.25 | libctf0 2.44-3 No fix yet | 0.2% 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-90802 | MEDIUM4.25 | libgprofng0 2.44-3 No fix yet | 0.2% 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-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-90802 | MEDIUM4.25 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2007-3303 | MEDIUM4.17 | apache2-data 2.4.68-1~deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | MEDIUM4.17 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-73636 | MEDIUM4.13 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | MEDIUM4.13 | curl 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-92392 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-86410 | MEDIUM4.08 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | MEDIUM4.03 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.41-12+deb13u4 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.44-3 No fix yet | 0.3% 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-18220 | 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-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.3% 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-18220 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW3.98 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW3.98 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | cpp-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | cpp-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | g++-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | g++-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | gcc-14 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW3.93 | gcc-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| 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-x86-64-linux-gnu 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92388 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-86414 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92390 | LOW3.9 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-46729 | LOW3.82 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56153 | LOW3.82 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63686 | LOW3.82 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63718 | LOW3.82 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% 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-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+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | curl 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9079 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.40.1-6+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-1743 | LOW3.74 | apache2 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2007-1743 | LOW3.74 | apache2-data 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u5 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-42528 | LOW3.65 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42528 | LOW3.65 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42528 | LOW3.65 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-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-2026-57941 | LOW3.57 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | cpp-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | cpp-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | g++-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | g++-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | gcc-14 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW3.57 | gcc-14-x86-64-linux-gnu 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | mount 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW3.57 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-19542 | LOW3.57 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | LOW3.57 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | LOW3.57 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.41-12+deb13u4 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.8-2 No fix yet | 4.9% Low-Moderate Risk | Post-Exploit |
| CVE-2026-90803 | LOW3.47 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90803 | LOW3.47 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW3.37 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90801 | LOW3.37 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90828 | LOW3.37 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90829 | LOW3.37 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90831 | LOW3.37 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% 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-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 8.14.1-2+deb13u5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | curl 8.14.1-2+deb13u5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-19931 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u5 fixed in 8.14.1-2+deb13u7 | 0.7% 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-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-2018-21232 | LOW3.3 | re2c 4.1-1 No fix yet | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2007-0086 | LOW3.23 | apache2-data 2.4.68-1~deb13u1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2007-0086 | LOW3.23 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-86409 | LOW3.18 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.41-12+deb13u4 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42356 | LOW3.15 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47360 | LOW3.15 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48005 | LOW3.15 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56449 | LOW3.15 | apache2 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42356 | LOW3.15 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47360 | LOW3.15 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48005 | LOW3.15 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56449 | LOW3.15 | apache2-bin 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42356 | LOW3.15 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-47360 | LOW3.15 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48005 | LOW3.15 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-56449 | LOW3.15 | apache2-data 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.15 | libc6-dev 2.41-12+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-90804 | LOW3.11 | binutils 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-2026-90804 | LOW3.11 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2008-0456 | LOW2.99 | apache2 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.99 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2008-0456 | LOW2.99 | apache2-data 2.4.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-15534 | LOW2.91 | perl 5.40.1-6+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-107928 | LOW2.88 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-73637 | LOW2.86 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils 2.44-3 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.44-3 No fix yet | 0.2% 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-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-59797 | LOW2.8 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% 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-19548 | 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-2026-90830 | LOW2.8 | binutils 2.44-3 No fix yet | 0.2% 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-19548 | 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-2026-90830 | LOW2.8 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.8 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.8-2 No fix yet | 0.8% 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-0+deb13u1 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.44-3 No fix yet | 0.4% 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.3% 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.44-3 No fix yet | 0.4% 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.3% 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.44-3 No fix yet | 0.4% 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.3% 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.44-3 No fix yet | 0.4% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.40 5.40.1-6+deb13u1 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.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libsframe1 2.44-3 No fix yet | 0.4% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u2 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.1% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86141 | LOW2.8 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-93546 | LOW2.75 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-dev-bin 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6-dev 2.41-12+deb13u4 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-5709 | LOW2.7 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2015-3276 | LOW2.7 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-17740 | LOW2.7 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | LOW2.7 | m4 1.4.19-8 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | LOW2.7 | m4 1.4.19-8 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | LOW2.7 | patch 2.8-2 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | LOW2.7 | patch 2.8-2 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58415 | LOW2.7 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63045 | LOW2.7 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-79768 | LOW2.7 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% 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-x86-64-linux-gnu 2.44-3 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libsframe1 2.44-3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1581 | LOW2.6 | apache2-data 2.4.68-1~deb13u1 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2003-1307 | LOW2.58 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2003-1580 | LOW2.58 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92386 | LOW2.58 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92386 | LOW2.58 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | 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-2026-90802 | LOW2.55 | binutils 2.44-3 No fix yet | 0.2% 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-90802 | LOW2.55 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2007-3303 | LOW2.5 | apache2-utils 2.4.68-1~deb13u1 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-56154 | LOW2.48 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-63292 | LOW2.48 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | curl 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | LOW2.48 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-82208 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% 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+deb13u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.5% 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-2007-1743 | LOW2.24 | apache2-utils 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | 0.1% 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-107929 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87863 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92387 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-107929 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87862 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87863 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87864 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87865 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-87866 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92387 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92389 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-92391 | LOW2.22 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-42528 | LOW2.19 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.04 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | — | Post-Exploit |
| CVE-2026-42356 | LOW1.89 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-47360 | LOW1.89 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48005 | LOW1.89 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-56449 | LOW1.89 | apache2-utils 2.4.68-1~deb13u1 fixed in 2.4.69-1~deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 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-13608 | LOW1.89 | curl 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | curl 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | curl 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13608 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-18924 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-80230 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-80255 | LOW1.89 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.5% 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.68-1~deb13u1 No fix yet | 19.0% High Exploitation Risk | Post-Exploit |
| CVE-2001-1534 | LOW1.78 | apache2 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-bin 2.4.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2001-1534 | LOW1.78 | apache2-data 2.4.68-1~deb13u1 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.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.44-3 No fix yet | 0.4% 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.3% 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.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.4% 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.3% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-2903 | LOW1.68 | re2c 4.1-1 No fix yet | 0.2% 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-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-2026-82209 | LOW1.58 | curl 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-82209 | LOW1.58 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2003-1581 | LOW1.56 | apache2-utils 2.4.68-1~deb13u1 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-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.68-1~deb13u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-99999 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89631 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89633 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11082 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11083 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5244 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-5245 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7545 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-7546 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18220 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6846 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 2.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89638 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89972 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97528 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98260 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78410 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-95619 | NONE0 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66864 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66866 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69649 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69650 | NONE0 | binutils-common 2.44-3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98417 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89610 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-3441 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3442 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97422 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97493 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2026-102010 | NONE0 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72463 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74520 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89675 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89811 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90111 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90206 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90315 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98222 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98320 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98323 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-98364 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98378 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68393 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72500 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74513 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89445 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89500 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89528 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-89534 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-89537 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89637 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89642 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89648 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89654 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89682 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89705 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89709 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-89766 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90093 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90099 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90104 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90142 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90146 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90161 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90177 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90234 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90237 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90240 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90256 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-90260 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90263 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90317 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90326 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90336 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90343 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90347 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93200 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97527 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97531 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97532 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97561 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97563 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97594 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97618 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97620 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97901 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97933 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97934 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97935 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97938 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97949 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97975 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97988 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98032 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98033 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98034 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98047 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98048 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98156 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98167 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98173 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98174 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98175 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98184 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98186 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98196 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98197 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98201 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98204 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98205 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98211 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98213 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98214 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98215 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98216 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98217 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98221 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98229 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98230 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98231 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98236 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98238 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98239 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98241 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98245 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98246 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98247 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98249 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98251 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98252 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98254 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98255 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98257 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98261 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98262 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98264 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98265 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98266 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98276 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98282 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98283 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98284 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98287 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98290 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98291 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98295 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98296 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98299 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98306 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98312 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98314 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98330 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98331 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98333 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98339 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98341 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98342 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98343 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98347 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98357 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98358 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98365 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98366 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98367 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98368 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98370 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98373 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98374 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98375 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98376 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98377 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98379 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98380 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98381 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98382 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98383 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98403 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98426 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98428 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98429 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98430 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98176 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98362 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90803 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93125 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-93144 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90801 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90828 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90829 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90831 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-20712 | NONE0 | binutils-common 2.44-3 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2021-32256 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90333 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98185 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-4647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90804 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90211 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1153 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-98271 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98432 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1178 | NONE0 | binutils-common 2.44-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-15003 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-13716 | NONE0 | binutils-common 2.44-3 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20673 | NONE0 | binutils-common 2.44-3 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-9996 | NONE0 | binutils-common 2.44-3 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-11081 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11412 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11413 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11414 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11494 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11495 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-11839 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-11840 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-3198 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-69651 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19548 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6844 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90830 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100072 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100074 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100076 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-100077 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23143 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68295 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68421 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72355 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72365 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72367 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72388 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74354 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74529 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74542 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80614 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80655 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80935 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80937 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80980 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-81010 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-81016 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89437 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89441 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89452 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89467 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89503 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89520 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89611 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89639 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89722 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89757 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89837 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89912 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89996 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90061 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90083 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90087 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90098 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90105 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90106 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90116 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90149 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90154 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90155 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90162 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-90174 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90179 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90204 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90205 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90208 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90217 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90231 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90232 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90247 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90259 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90264 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90265 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90273 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90289 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90300 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90301 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-90320 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90321 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90324 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90328 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90337 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90345 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90422 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93196 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93270 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93272 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93276 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93282 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-93285 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97432 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97478 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97499 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97513 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97515 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97526 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97529 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97534 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97535 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97536 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97537 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97538 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97554 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97558 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97559 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97565 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97567 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97571 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97574 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97603 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97609 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97918 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97919 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97939 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97950 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97960 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97962 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98019 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98043 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98049 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98053 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98062 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98115 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98118 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98131 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98134 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98161 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98162 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98168 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98169 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98170 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98172 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98180 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98187 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98188 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98189 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98190 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98192 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98193 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98194 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98195 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98198 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98199 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98200 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98206 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98207 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98209 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98210 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98212 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98218 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98227 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98228 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98248 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98253 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98267 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98269 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98272 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98277 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98279 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98288 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98292 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98293 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98294 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98298 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98302 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98303 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98309 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98311 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98313 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98322 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98327 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98335 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98336 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98340 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98348 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98349 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-98351 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98352 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98353 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98355 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98359 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98360 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98369 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98384 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98407 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98408 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98409 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98410 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98413 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98419 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98420 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98423 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68375 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72366 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72497 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74728 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80705 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80939 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80948 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89527 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89601 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89862 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90084 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90097 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90144 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90182 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90183 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90261 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90267 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90306 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90311 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90330 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90335 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90346 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90424 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92493 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93116 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93199 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93202 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97424 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97477 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97479 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97480 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97501 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97503 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-97530 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97549 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97566 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97597 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97615 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97619 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97906 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97928 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97989 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-97997 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98003 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98038 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98044 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98058 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98067 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98073 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98087 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98119 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98124 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98125 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98147 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98148 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98177 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98179 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98182 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98191 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98202 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98203 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98208 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98233 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98234 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98235 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98237 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98263 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98270 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98285 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98289 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98297 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98304 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98307 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98308 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98317 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98319 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98321 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98325 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98326 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98328 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98329 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98332 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98334 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98337 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98338 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98344 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98345 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98346 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98386 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98389 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98393 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98406 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98421 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98422 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98424 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98425 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98427 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98431 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90086 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1147 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98300 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1176 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1181 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-1182 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-6845 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-90802 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 2.9% Low-Moderate Risk | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98301 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98354 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-98181 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98273 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98435 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98101 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98363 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-98286 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98411 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98412 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98416 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-1152 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-66861 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66862 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66863 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-66865 | NONE0 | binutils-common 2.44-3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69647 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69648 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69652 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-8225 | NONE0 | binutils-common 2.44-3 No fix yet | 0.3% 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-2015-2877 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-1148 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1149 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1150 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1151 | NONE0 | binutils-common 2.44-3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-1180 | NONE0 | binutils-common 2.44-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-69644 | NONE0 | binutils-common 2.44-3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69645 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-69646 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-98433 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b10 No fix yet | — | Not Applicable |
| CVE-2026-91779 | NONE0 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | binutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | binutils-common 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | binutils-x86-64-linux-gnu 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | curl 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libbinutils 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libctf-nobfd0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libctf0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl4t64 8.14.1-2+deb13u5 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-95184 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95209 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-95210 | NONE0 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libgprofng0 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| DSA-6549-1 | NONE0 | liblzma5 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | liblzma5 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| CVE-2026-82560 | NONE0 | libperl5.40 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-91779 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91780 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91781 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-91782 | NONE0 | libsframe1 2.44-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-93221 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89788 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89810 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89913 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90167 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90417 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92499 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93105 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93148 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93154 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93175 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93176 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98084 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98085 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98171 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80920 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89806 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89808 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89812 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89813 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89826 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89827 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89832 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89833 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89840 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89866 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89868 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89906 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89935 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89956 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89971 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-89987 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90016 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90029 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90030 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90040 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90156 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90409 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90427 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92480 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92485 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92500 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92503 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92518 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92520 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93044 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93135 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93179 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93243 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93244 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98079 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98099 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98232 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98275 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98316 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89795 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89797 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89838 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89859 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89920 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89921 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90002 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90013 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90023 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90351 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90359 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90363 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90365 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90367 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90379 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-90401 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90408 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-90421 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-92482 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93047 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93058 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93081 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93099 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93100 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93104 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93122 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93129 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93146 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93168 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93181 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93216 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93230 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93231 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93237 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93251 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-93260 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | — | Not Applicable |
| CVE-2026-98436 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98439 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98440 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98441 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98442 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98443 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98444 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98445 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98448 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98449 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98450 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98451 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98452 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98453 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98454 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98455 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98456 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98457 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98458 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98459 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98460 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98461 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98462 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98464 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98465 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98466 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98468 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98471 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98473 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98475 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98476 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98477 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98479 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98481 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98482 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98483 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98484 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98485 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98486 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98487 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98488 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98489 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98490 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98491 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98493 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98494 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98495 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98498 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98499 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98501 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98502 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98503 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98504 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98505 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98506 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98507 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98508 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98509 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98510 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98511 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98512 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98513 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98514 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98515 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98516 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98517 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98519 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98521 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98522 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98523 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98524 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98525 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98526 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98527 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98528 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98529 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98531 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98532 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98533 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98534 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98535 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98536 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98537 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98538 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98539 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98541 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98544 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98545 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98546 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98547 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98548 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98549 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98550 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98551 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98553 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98554 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98555 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98556 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98558 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98559 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98561 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98565 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98566 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98567 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98568 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98569 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98570 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98572 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98573 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98575 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98576 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98577 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98578 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98579 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98580 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98581 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98582 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98583 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98586 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98588 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98589 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98590 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98591 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98593 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98594 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98596 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98597 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98598 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98599 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98600 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98601 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98602 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98605 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98606 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98607 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98608 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98609 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98610 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98611 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98612 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98613 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98614 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98615 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98616 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98618 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98620 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98621 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98622 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98623 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98624 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98625 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98626 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98628 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98629 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98631 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98632 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98634 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98636 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98640 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98641 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98642 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98643 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98644 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98646 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98647 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98652 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98655 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98656 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98657 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98658 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98660 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98661 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98662 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98663 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98664 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98665 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98666 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98668 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98669 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98670 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98671 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98672 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98673 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98674 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98677 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98679 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98680 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98681 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98682 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98683 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98684 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98685 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98686 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98687 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98694 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98695 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98696 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98697 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98698 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98699 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98700 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98701 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98702 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98703 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98704 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98705 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98706 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98707 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98708 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98709 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98710 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98711 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98713 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98714 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98715 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98716 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98717 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98720 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98721 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98722 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98725 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98726 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98727 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98728 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98730 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98731 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98732 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98733 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98734 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98735 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98736 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98737 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98738 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98739 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98740 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98741 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98742 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98743 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98744 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98745 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98746 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98747 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98748 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98749 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98750 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98751 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98752 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98753 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98754 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98755 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98756 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98757 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98758 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98760 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98761 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98762 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98763 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98764 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98765 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98766 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98767 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98768 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98769 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98770 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98771 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98772 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98773 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98775 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98777 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98778 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98779 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98780 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98781 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98782 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98783 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98784 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98785 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98786 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98789 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98790 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98791 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98792 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98793 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98794 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98795 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98796 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98797 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98798 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98799 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98800 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98801 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98802 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98803 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98805 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98807 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98808 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98809 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98810 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98811 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98812 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98813 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98814 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98815 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98816 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98819 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98820 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98822 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98823 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98824 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98825 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98826 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98827 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98828 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98829 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98830 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98831 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98833 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98834 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98835 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98836 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98837 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98838 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98839 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98840 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98841 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98843 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98844 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98845 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98846 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98847 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98848 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98849 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98850 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98851 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98852 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98853 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-98854 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98855 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98856 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98857 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98858 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98859 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98860 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98862 | NONE0 | linux-libc-dev 6.12.111-1 fixed in 6.12.113-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-98863 | NONE0 | linux-libc-dev 6.12.111-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-82560 | NONE0 | perl 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-base 5.40.1-6+deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-82560 | NONE0 | perl-modules-5.40 5.40.1-6+deb13u1 No fix yet | 0.6% 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 |
| DSA-6549-1 | NONE0 | xz-utils 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| TEMP-1147318-639065 | NONE0 | xz-utils 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.4% 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 | 15.7% High Exploitation Risk | 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.3% 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.6% 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.3% 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.3% 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 |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.