Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit CVE-2023-44487 to cause denial of service via HTTP/2 stream resets, and exploit CVE-2026-57432 for remote code execution or heap memory disclosure, potentially compromising the host. The image's trust from a reputable publisher does not mitigate these severe vulnerabilities.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-44487 | CRITICAL9.75 | nginx 1.23.0-1~bullseye No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-57432 | HIGH8.4 | libperl5.32 5.32.1-4+deb11u5 No fix yet | — | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgbm-dev 20.3.5-1 fixed in 20.3.5-1+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgbm1 20.3.5-1 fixed in 20.3.5-1+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgl1-mesa-dri 20.3.5-1 fixed in 20.3.5-1+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libglapi-mesa 20.3.5-1 fixed in 20.3.5-1+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libglx-mesa0 20.3.5-1 fixed in 20.3.5-1+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.10+dfsg-6.7+deb11u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23112 | HIGH8.33 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | mesa-vulkan-drivers 20.3.5-1 fixed in 20.3.5-1+deb11u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2008-4609 | HIGH8.16 | linux-libc-dev 5.10.251-1 No fix yet | 32.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | HIGH8.1 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42010 | HIGH7.84 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2013-0340 | HIGH7.82 | libexpat1 2.2.10-2+deb11u7 No fix yet | 19.4% High Exploitation Risk | Directly Exposed |
| CVE-2009-4487 | HIGH7.82 | nginx 1.23.0-1~bullseye No fix yet | 27.0% High Exploitation Risk | Directly Exposed |
| CVE-2021-45078 | HIGH7.8 | libbinutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45078 | HIGH7.8 | libctf-nobfd0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45078 | HIGH7.8 | libctf0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre16-3 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre16-3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre3 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre3-dev 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre3-dev 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcre32-3 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcre32-3 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7245 | HIGH7.8 | libpcrecpp0v5 2:8.39-13 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7246 | HIGH7.8 | libpcrecpp0v5 2:8.39-13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 5.10.251-1 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19449 | HIGH7.8 | linux-libc-dev 5.10.251-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 5.10.251-1 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46300 | HIGH7.8 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46333 | HIGH7.8 | linux-libc-dev 5.10.251-1 fixed in 5.10.251-5 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-64600 | HIGH7.8 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 5.10.251-1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 5.10.251-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2369 | HIGH7.73 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2369 | HIGH7.73 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3530 | HIGH7.5 | libbinutils 2.35.2-2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3530 | HIGH7.5 | libctf-nobfd0 2.35.2-2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3530 | HIGH7.5 | libctf0 2.35.2-2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-8176 | HIGH7.5 | libexpat1 2.2.10-2+deb11u7 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.2.10-2+deb11u7 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2021-33560 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.8.7-6 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-25193 | HIGH7.5 | libharfbuzz0b 2.7.4-1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libip4tc2 1.8.7-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre16-3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre16-3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre3-dev 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre3-dev 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcre32-3 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcre32-3 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11164 | HIGH7.5 | libpcrecpp0v5 2:8.39-13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-20838 | HIGH7.5 | libpcrecpp0v5 2:8.39-13 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15709 | HIGH7.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15711 | HIGH7.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15709 | HIGH7.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15711 | HIGH7.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4899 | HIGH7.5 | libzstd1 1.4.8+dfsg-2.1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-49997 | HIGH7.5 | linux-libc-dev 5.10.251-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 5.10.251-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 5.10.251-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2013-0337 | HIGH7.5 | nginx 1.23.0-1~bullseye No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2020-19726 | HIGH7.48 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-19726 | HIGH7.48 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2020-19726 | HIGH7.48 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-56001 | HIGH7.48 | libxfont2 1:2.0.4-1 fixed in 1:2.0.4-1+deb11u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-56002 | HIGH7.48 | libxfont2 1:2.0.4-1 fixed in 1:2.0.4-1+deb11u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56003 | HIGH7.48 | libxfont2 1:2.0.4-1 fixed in 1:2.0.4-1+deb11u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43037 | HIGH7.48 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-47659 | HIGH7.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23395 | HIGH7.48 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0719 | HIGH7.31 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1761 | HIGH7.31 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-0719 | HIGH7.31 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1761 | HIGH7.31 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-10263 | HIGH7.14 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | HIGH7.1 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | — | Directly Exposed |
| CVE-2026-16118 | HIGH7.1 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | — | Directly Exposed |
| CVE-2026-16118 | HIGH7.1 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | — | Directly Exposed |
| CVE-2021-4204 | HIGH7.1 | linux-libc-dev 5.10.251-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53398 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53399 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63824 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63829 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63830 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63831 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63875 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63887 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63888 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63899 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63917 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63921 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63922 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63924 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63956 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63962 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63993 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63994 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64007 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64009 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64026 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64113 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64191 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53381 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53384 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53388 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53391 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53392 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53393 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53397 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63794 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63800 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63801 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63808 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63809 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63823 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63826 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63891 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63898 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63901 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63912 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63913 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63914 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63916 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63919 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63920 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63925 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63928 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63947 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63957 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63958 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63971 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63975 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63984 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63992 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64001 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64002 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64011 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64015 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64025 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64047 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64048 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64098 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64102 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64109 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64114 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64115 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64174 | HIGH7 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64189 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64192 | HIGH7 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-42533 | HIGH7 | nginx 1.23.0-1~bullseye No fix yet | — | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-14523 | MEDIUM6.97 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2436 | MEDIUM6.97 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5119 | MEDIUM6.97 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14523 | MEDIUM6.97 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2436 | MEDIUM6.97 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5119 | MEDIUM6.97 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31788 | MEDIUM6.97 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6-dev 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM6.88 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16615 | MEDIUM6.8 | librest-0.7-0 0.8.1-1.1 No fix yet | — | Directly Exposed |
| CVE-2023-24023 | MEDIUM6.8 | linux-libc-dev 5.10.251-1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-15794 | MEDIUM6.7 | linux-libc-dev 5.10.251-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2022-44840 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45703 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47673 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47695 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47696 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1579 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-44840 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45703 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47673 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47695 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47696 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1579 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-44840 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-45703 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47673 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47695 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-47696 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1579 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1 0.183-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1 0.183-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-31782 | MEDIUM6.63 | libfreetype6 2.10.4+dfsg-1+deb11u2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | MEDIUM6.63 | libnss3 2:3.61-1+deb11u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.10+dfsg-6.7+deb11u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-12362 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-47014 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47028 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47200 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47653 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0500 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48626 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48674 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49359 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49470 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49635 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49722 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49935 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49980 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50050 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50070 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50151 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50163 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50256 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50300 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50378 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50406 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50492 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50518 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50552 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52494 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52531 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52664 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52916 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53039 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53072 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53111 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53282 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53432 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53473 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53510 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53544 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53577 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53596 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53673 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-23307 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-26589 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26792 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26865 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26913 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26914 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26996 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35863 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35864 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35868 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35932 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36880 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36898 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36914 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38545 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38556 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38581 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-38667 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40927 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41069 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42147 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42160 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42271 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43900 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44934 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44941 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44949 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44986 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45026 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46830 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46859 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46871 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47695 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47745 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49924 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49950 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49989 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49991 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49992 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50051 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50063 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50067 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50125 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53165 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53213 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56551 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56604 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56609 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56614 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-56640 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56651 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56775 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57798 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57849 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58034 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58240 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21734 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21780 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21812 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21855 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22083 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37786 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37849 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37903 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37928 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-37991 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38068 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38129 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38250 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38257 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38259 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38280 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38361 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38422 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38527 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38585 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38685 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38702 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39686 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39790 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39863 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39873 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40149 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71078 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71082 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71089 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23068 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23111 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23221 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23227 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23231 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-23281 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23378 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31399 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31402 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31452 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31455 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31485 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31720 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31747 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31748 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31759 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31787 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43015 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43020 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43027 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43196 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43328 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43329 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43426 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43458 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43499 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45839 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45866 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45867 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45879 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45885 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45914 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45916 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45920 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45936 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45984 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46075 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46122 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46243 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46267 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46285 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46301 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52943 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52962 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52992 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53004 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53059 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53089 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53112 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53115 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53117 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53120 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53129 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53136 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53137 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53148 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53156 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53157 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53195 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53262 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53294 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53296 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53359 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-22995 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 5.10.251-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 5.10.251-1 No fix yet | 7.2% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.35.2-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libbinutils 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-gobject2 1.16.0-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.16.0-5 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2 1.16.0-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2 1.16.0-5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.35.2-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libctf-nobfd0 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.35.2-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3826 | MEDIUM6.5 | libctf0 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-3.1+b2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6129 | MEDIUM6.5 | libpng-dev 1.6.37-3+deb11u3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6129 | MEDIUM6.5 | libpng16-16 1.6.37-3+deb11u3 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15714 | MEDIUM6.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-66337 | MEDIUM6.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-66339 | MEDIUM6.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15714 | MEDIUM6.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-66337 | MEDIUM6.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-66339 | MEDIUM6.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1192 | MEDIUM6.5 | linux-libc-dev 5.10.251-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 5.10.251-1 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2021-46174 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-42523 | MEDIUM6.38 | libcolord2 1.4.5-3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2021-46174 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-46174 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM6.38 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.183-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.18.3-6+deb11u7 fixed in 1.18.3-6+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41254 | MEDIUM6.38 | liblcms2-2 2.12~rc1-2 fixed in 2.12~rc1-2+deb11u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.43.0-1+deb11u2 fixed in 1.43.0-1+deb11u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-16-0 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-32-0 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-8-0 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-dev 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-41409 | MEDIUM6.38 | libpcre2-posix2 10.36-2+deb11u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.9-stdlib 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.9-stdlib 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-4271 | MEDIUM6.38 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32049 | MEDIUM6.38 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-4271 | MEDIUM6.38 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32049 | MEDIUM6.38 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-32256 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-42225 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53266 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43190 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53071 | MEDIUM6.38 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-21758 | MEDIUM6.32 | linux-libc-dev 5.10.251-1 No fix yet | 13.0% High Exploitation Risk | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3099 | MEDIUM6.21 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3099 | MEDIUM6.21 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43038 | MEDIUM6.21 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23243 | MEDIUM6.21 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43078 | MEDIUM6.21 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libnss-systemd 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libsystemd0 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | MEDIUM6.1 | libudev1 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.2.53-10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3549 | MEDIUM6.03 | libbinutils 2.35.2-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-25584 | MEDIUM6.03 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3549 | MEDIUM6.03 | libctf-nobfd0 2.35.2-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-25584 | MEDIUM6.03 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3549 | MEDIUM6.03 | libctf0 2.35.2-2 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-25584 | MEDIUM6.03 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-47101 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3566 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49172 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49218 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49234 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49289 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49444 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49509 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49623 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49961 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50026 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50255 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50306 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52588 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52682 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52766 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53254 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35939 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36915 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41013 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41014 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46774 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49861 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57945 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22107 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37879 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38159 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38502 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38679 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38728 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39685 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40082 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23099 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23204 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23315 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23318 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23388 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23397 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31778 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43040 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43141 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43241 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43281 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43386 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43427 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43449 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43450 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43453 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45893 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53138 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53149 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53255 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53303 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53309 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53330 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53751 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25743 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23455 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31786 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43051 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46259 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-32078 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-47094 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6610 | MEDIUM6.03 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.44-1+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2021-39686 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42162 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47747 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50061 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57876 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39759 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39826 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71221 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43050 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43503 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52989 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52991 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52993 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53002 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53006 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53091 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49328 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57984 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40135 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23392 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31408 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31508 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43158 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43226 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43233 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43334 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43339 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45856 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45860 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45970 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46174 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52912 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52917 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52918 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52920 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52924 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52935 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52942 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52947 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52956 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52957 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52986 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52998 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53009 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53011 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53016 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53036 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53049 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53053 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53062 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53072 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53075 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53078 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53131 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53133 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53185 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53189 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53212 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53223 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53224 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53228 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53230 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53239 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53242 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53246 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53253 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53254 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53256 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53264 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53268 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53270 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53275 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53354 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53355 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53357 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23054 | MEDIUM5.95 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc-bin 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc-bin 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4806 | MEDIUM5.9 | libc6-dev 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2023-4813 | MEDIUM5.9 | libc6-dev 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.8.7-6 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-15712 | MEDIUM5.9 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15713 | MEDIUM5.9 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15712 | MEDIUM5.9 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-15713 | MEDIUM5.9 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.16.0-2+deb11u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 5.10.251-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 5.10.251-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-46421 | MEDIUM5.78 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-46421 | MEDIUM5.78 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53196 | MEDIUM5.78 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM5.7 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50616 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26828 | MEDIUM5.7 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-3782 | MEDIUM5.61 | libwayland-client0 1.18.0-2~exp1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3782 | MEDIUM5.61 | libwayland-cursor0 1.18.0-2~exp1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3782 | MEDIUM5.61 | libwayland-egl1 1.18.0-2~exp1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-3782 | MEDIUM5.61 | libwayland-server0 1.18.0-2~exp1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-50851 | MEDIUM5.61 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40261 | MEDIUM5.61 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53267 | MEDIUM5.61 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.1-5+deb11u9 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.35.2-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.35.2-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.35.2-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | MEDIUM5.52 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | libnss3 2:3.61-1+deb11u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.40.0-1.1~deb11u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-46420 | MEDIUM5.52 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1801 | MEDIUM5.52 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3633 | MEDIUM5.52 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3634 | MEDIUM5.52 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-46420 | MEDIUM5.52 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1801 | MEDIUM5.52 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3633 | MEDIUM5.52 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3634 | MEDIUM5.52 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-40090 | MEDIUM5.52 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 5.10.251-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47693 | MEDIUM5.52 | linux-libc-dev 5.10.251-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53176 | MEDIUM5.52 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.35.2-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.35.2-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libbinutils 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20284 | MEDIUM5.5 | libbinutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.16.0-5 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.16.0-5 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.35.2-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.35.2-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf-nobfd0 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20284 | MEDIUM5.5 | libctf-nobfd0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.35.2-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.35.2-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010204 | MEDIUM5.5 | libctf0 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-20284 | MEDIUM5.5 | libctf0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-33068 | MEDIUM5.5 | libharfbuzz0b 2.7.4-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2021-46822 | MEDIUM5.5 | libjpeg62-turbo 1:2.0.6-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1056 | MEDIUM5.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53400 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53402 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63803 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63822 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63858 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63860 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63868 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63870 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63890 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63892 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63893 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63897 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63900 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63902 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63903 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63904 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63926 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63927 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63942 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63948 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63961 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63963 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63976 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63983 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64004 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64005 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64006 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64012 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64014 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64046 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64103 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64106 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64112 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64118 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64123 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64125 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64133 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64170 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64173 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64177 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64178 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64185 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64190 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64206 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53369 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-53379 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53385 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-53403 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63810 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63872 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63964 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-63990 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-63991 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Directly Exposed |
| CVE-2026-64144 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-64187 | MEDIUM5.5 | linux-libc-dev 5.10.251-1 No fix yet | — | Directly Exposed |
| CVE-2026-13221 | MEDIUM5.46 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2022-3567 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-21823 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23456 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52910 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53090 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2574 | MEDIUM5.4 | glib-networking 2.66.0-2 No fix yet | — | Directly Exposed |
| CVE-2026-2574 | MEDIUM5.4 | glib-networking-common 2.66.0-2 No fix yet | — | Directly Exposed |
| CVE-2026-2574 | MEDIUM5.4 | glib-networking-services 2.66.0-2 No fix yet | — | Directly Exposed |
| CVE-2026-66338 | MEDIUM5.4 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-66338 | MEDIUM5.4 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.2.53-10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.4.48-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-20197 | MEDIUM5.35 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-20197 | MEDIUM5.35 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-20197 | MEDIUM5.35 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27447 | MEDIUM5.35 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-1280 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26830 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57893 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31504 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | gir1.2-gdkpixbuf-2.0 2.42.2+dfsg-1+deb11u5 No fix yet | — | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.2.10-2+deb11u7 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf-2.0-0 2.42.2+dfsg-1+deb11u5 No fix yet | — | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf-2.0-dev 2.42.2+dfsg-1+deb11u5 No fix yet | — | Directly Exposed |
| CVE-2026-16768 | MEDIUM5.3 | libgdk-pixbuf2.0-common 2.42.2+dfsg-1+deb11u5 No fix yet | — | Directly Exposed |
| CVE-2026-15588 | MEDIUM5.3 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | — | Directly Exposed |
| CVE-2026-15588 | MEDIUM5.3 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | — | Directly Exposed |
| CVE-2026-15588 | MEDIUM5.3 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | — | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.34-4+deb11u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | MEDIUM5.28 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | MEDIUM5.28 | libc-devtools 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-32006 | MEDIUM5.28 | nodejs 24.14.1-1nodesource1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28292 | MEDIUM5.28 | simple-git 3.16.0 fixed in 3.32.3 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39314 | MEDIUM5.27 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | MEDIUM5.27 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.23.22-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng-dev 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.10+dfsg-6.7+deb11u9 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50764 | MEDIUM5.27 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54081 | MEDIUM5.27 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23253 | MEDIUM5.27 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount-dev 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6766 | MEDIUM5.18 | libnss3 2:3.61-1+deb11u5 fixed in 2:3.61-1+deb11u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6767 | MEDIUM5.18 | libnss3 2:3.61-1+deb11u5 fixed in 2:3.61-1+deb11u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6772 | MEDIUM5.18 | libnss3 2:3.61-1+deb11u5 fixed in 2:3.61-1+deb11u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53840 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53850 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40080 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40279 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68343 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31464 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31570 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43134 | MEDIUM5.18 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | uuid-dev 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-43551 | MEDIUM5.17 | curl 7.74.0-1.3+deb11u16 No fix yet | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2022-43551 | MEDIUM5.17 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 16.5% High Exploitation Risk | Post-Exploit |
| CVE-2026-31649 | MEDIUM5.1 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52481 | MEDIUM5.1 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | MEDIUM5.04 | perl 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | MEDIUM5.04 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | MEDIUM5.04 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6-dev 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9901 | MEDIUM5.02 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-9901 | MEDIUM5.02 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.10+dfsg-6.7+deb11u9 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-50666 | MEDIUM5.02 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32253 | MEDIUM5.02 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-54048 | MEDIUM5.02 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35870 | MEDIUM5.02 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40242 | MEDIUM5.02 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48930 | MEDIUM5 | nodejs 24.14.1-1nodesource1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | MEDIUM5 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0 2.66.8-1+deb11u8 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-data 2.66.8-1+deb11u8 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev 2.66.8-1+deb11u8 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 5.10.251-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1539 | MEDIUM4.93 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1539 | MEDIUM4.93 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50635 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40323 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68742 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-23271 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31392 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31414 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31426 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43279 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52923 | MEDIUM4.93 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl 5.32.1-4+deb11u5 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-base 5.32.1-4+deb11u5 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | MEDIUM4.86 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-31431 | MEDIUM4.86 | linux-libc-dev 5.10.251-1 fixed in 5.10.251-3 | 96.3% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2026-43284 | MEDIUM4.86 | linux-libc-dev 5.10.251-1 fixed in 5.10.251-4 | 93.2% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2026-43500 | MEDIUM4.86 | linux-libc-dev 5.10.251-1 fixed in 5.10.251-4 | 92.8% Actively Exploited | Post-ExploitContext importance: MEDIUM |
| CVE-2022-49138 | MEDIUM4.84 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-54251 | MEDIUM4.76 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-1010022 | MEDIUM4.7 | libc-bin 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2019-1010022 | MEDIUM4.7 | libc6 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-ExploitContext importance: MEDIUM |
| CVE-2024-2201 | MEDIUM4.7 | linux-libc-dev 5.10.251-1 No fix yet | 8.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 5.10.251-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45078 | MEDIUM4.68 | binutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45078 | MEDIUM4.68 | binutils-common 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45078 | MEDIUM4.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-35205 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-35206 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-38533 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4285 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47007 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47008 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48063 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-48065 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-25585 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25586 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25588 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-35205 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-35206 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-38533 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4285 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47007 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47008 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48063 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-48065 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-25585 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25586 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25588 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-46195 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-35205 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-35206 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-38533 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-4285 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47007 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47008 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47010 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-47011 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48063 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48064 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-48065 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-25585 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-25586 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-25588 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | MEDIUM4.67 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-33294 | MEDIUM4.67 | libelf1 0.183-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1 0.183-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1 0.183-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount-dev 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre16-3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre3-dev 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcre32-3 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-16231 | MEDIUM4.67 | libpcrecpp0v5 2:8.39-13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.37-3+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.37-3+deb11u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3632 | MEDIUM4.67 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3632 | MEDIUM4.67 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-30775 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4367 | MEDIUM4.67 | libxpm4 1:3.5.12-1.1+deb11u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.34-4+deb11u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68307 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-12363 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-12364 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-24504 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-33061 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-4023 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4149 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-46926 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-46937 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47036 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47105 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-47182 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47188 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47199 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47205 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47211 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47212 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47265 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47275 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47366 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47381 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47410 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47448 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47452 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47504 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47508 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47552 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47558 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47582 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47610 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47618 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47622 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47658 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0480 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3108 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3114 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-3344 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-38457 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-40133 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-48628 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48633 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48645 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48673 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48703 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48721 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48765 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48811 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48814 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48833 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48859 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48862 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48887 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48901 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48902 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48920 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48944 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48952 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48961 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48975 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48979 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49004 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49034 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49069 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49096 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49102 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49106 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49109 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49110 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49112 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49123 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49124 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49128 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49132 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49134 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49135 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49142 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49157 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49158 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49160 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49161 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49164 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49169 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49173 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49178 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49182 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49183 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49214 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49226 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49246 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49266 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49285 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49294 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49296 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49306 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49311 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49317 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49325 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49342 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49390 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49398 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49420 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49428 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49437 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49440 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49469 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49496 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49504 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49513 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49528 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49531 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49533 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49534 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49536 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49543 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49562 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49563 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49564 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49566 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49591 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49610 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49616 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49617 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49622 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49650 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49651 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49654 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49666 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49742 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49758 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49764 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49765 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49766 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49801 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49803 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49822 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49828 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49829 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49837 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49858 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49898 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49901 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49932 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49938 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-49997 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50000 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50009 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50011 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50015 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50016 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50023 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50053 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50060 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50073 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50086 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50098 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50100 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50111 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50114 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50116 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50120 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50144 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50159 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50166 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50167 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50224 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50233 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50236 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50260 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50266 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50267 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50293 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50304 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50316 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50335 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50380 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50390 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50392 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50393 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50399 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50407 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50418 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50420 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50428 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50445 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50461 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50469 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50472 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50493 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50500 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50527 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50539 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50541 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50550 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50554 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50627 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50642 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50746 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50772 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50822 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50871 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-4569 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52593 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52610 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52652 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52660 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52677 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52680 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52700 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52732 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52762 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52763 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52808 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52815 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52834 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52878 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52913 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52918 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52939 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53002 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53008 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53010 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53042 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53055 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53068 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53074 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53091 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53093 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53103 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53105 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53133 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53152 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53200 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53221 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53244 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53248 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53250 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53270 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53287 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53332 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53335 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53347 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53348 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53355 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53370 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53383 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53393 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53415 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53421 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53438 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53441 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53458 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53466 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53470 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53476 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53482 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53499 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53509 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53513 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53539 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53540 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53545 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53562 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53579 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53584 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53588 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53594 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53597 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53602 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53618 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53620 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53635 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53647 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53651 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53661 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53682 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53685 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53753 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53765 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53780 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53806 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53822 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53829 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53849 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53856 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54028 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54129 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26584 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26595 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26656 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26668 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26680 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26700 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26706 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26715 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26718 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26726 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26759 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26795 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26807 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26844 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26893 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26896 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26920 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27002 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27014 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27032 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27034 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27035 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27037 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27054 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27056 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27389 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27402 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27403 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35803 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35817 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35826 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35839 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35840 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35844 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35875 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35938 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35956 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35971 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35995 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36000 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36009 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36023 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36029 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36244 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36478 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-36479 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36897 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36917 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36924 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36969 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37021 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38543 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38553 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38554 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38602 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38620 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38632 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39472 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39490 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39507 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40910 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40911 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40915 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40966 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40967 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40969 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40972 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40973 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40977 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41001 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41002 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41036 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41048 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41062 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41079 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41088 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41093 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42063 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42068 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42080 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42098 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42110 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42122 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42129 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42252 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42267 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42296 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42319 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42321 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43817 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43819 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43823 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43831 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43832 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43901 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43902 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43904 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43909 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43912 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44939 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44950 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44958 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44969 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44982 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45009 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45828 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46715 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46716 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46720 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46726 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46732 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46733 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46752 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46760 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46761 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46770 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46772 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46773 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46776 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46802 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46807 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46810 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46826 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46832 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46848 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46857 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47408 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47665 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47667 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47669 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47673 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47678 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47683 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47690 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47704 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47720 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47728 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47809 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49891 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49897 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49898 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49899 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49905 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49911 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49912 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49915 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49917 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49925 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-49927 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49929 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49954 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49978 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50002 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50003 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50038 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50060 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50062 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50138 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50168 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50187 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50196 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50256 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50258 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50272 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50298 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53058 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53093 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53094 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53122 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53128 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53190 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53196 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53210 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53220 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53234 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56369 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56557 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56584 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56590 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56647 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56703 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56715 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56718 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56722 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56746 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56776 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56777 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56778 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56785 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56787 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57897 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57903 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57924 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57939 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21629 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21682 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21690 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21712 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21738 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21750 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21766 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21792 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21816 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21820 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21838 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21839 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21866 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21881 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21891 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21899 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21931 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22026 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22071 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22072 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22073 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22090 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23161 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37742 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37758 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37820 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37852 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37883 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37911 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37925 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37951 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37959 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37961 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37967 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37980 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38040 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38057 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38062 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38063 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38097 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38105 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38125 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38126 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38148 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38162 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38166 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38192 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38215 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38262 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38300 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38310 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38319 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38331 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38362 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38408 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38409 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38410 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38436 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38491 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38499 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38576 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38614 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38623 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38624 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38626 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38630 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38643 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38644 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38645 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38659 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38665 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38696 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39675 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39684 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39693 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39706 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39716 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39748 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39763 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39764 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39770 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39772 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39773 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39800 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39801 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39819 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39827 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39929 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39931 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40005 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40104 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40164 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68223 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68231 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68283 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68340 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68358 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71081 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71083 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71121 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71161 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71183 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71268 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71269 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71287 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71292 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71297 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71304 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71305 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23019 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23031 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23069 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23086 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23100 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23141 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23154 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23157 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23242 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23267 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23273 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23274 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23277 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23279 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23286 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23287 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23289 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23290 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23291 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23292 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23293 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23296 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23298 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23300 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23303 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23304 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23307 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23312 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23336 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23339 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23340 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23351 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23352 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23356 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23357 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23362 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23365 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23367 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23368 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23379 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23381 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23382 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23391 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23396 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23398 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23420 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23434 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23439 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23446 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23449 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23460 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23462 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23474 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31391 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31400 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31403 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31411 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31412 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31415 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31416 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31418 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31421 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31422 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31423 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31424 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31425 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31427 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31428 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31441 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31446 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31447 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31448 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31450 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31453 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31454 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31469 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31473 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31495 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31496 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31497 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31498 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31503 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31507 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31509 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31510 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31512 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31515 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31518 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31519 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31521 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31524 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31540 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31545 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31546 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31548 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31550 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31552 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31555 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31628 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31634 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31651 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31658 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31660 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31661 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31662 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31664 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31665 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31667 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31670 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31671 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31672 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31674 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31678 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31679 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31680 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31682 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31721 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31726 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31737 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31738 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31749 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31752 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31754 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31755 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31758 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31762 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31763 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31770 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31773 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31781 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43014 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43024 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43025 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43026 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43028 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43032 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43033 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.251-3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43035 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43041 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43043 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43046 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43060 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43061 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43062 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43066 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43068 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43069 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43077 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43123 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43124 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43130 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43132 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43135 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43136 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43139 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43140 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43143 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43147 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43149 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43152 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43156 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43159 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43162 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43168 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43171 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43180 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43182 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43183 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43187 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43202 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43209 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43218 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43223 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43225 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43227 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43230 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43231 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43242 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43246 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43251 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43255 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43257 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43261 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43262 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43264 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43266 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43268 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43269 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43270 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43273 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43277 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43287 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43289 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43295 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43296 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43302 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43313 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43314 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43316 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43327 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43340 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43343 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43355 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43357 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43359 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43361 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43363 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43381 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43382 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43387 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43407 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43411 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43424 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43425 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43428 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43429 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43432 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43437 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43445 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43451 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43452 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43459 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43466 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43472 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43475 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43480 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43483 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43484 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45848 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45850 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45857 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45862 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45868 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45869 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45870 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45871 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45873 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45875 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45883 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45890 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45904 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45912 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45915 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45919 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45923 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45940 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45941 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45948 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45954 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45960 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45964 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45965 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45968 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45974 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45978 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45983 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46028 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46077 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46080 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46091 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46098 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46108 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46109 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46128 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46247 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46249 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46253 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46276 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46303 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52909 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52913 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52915 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52916 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52921 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52925 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52926 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52927 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52929 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52930 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52936 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52937 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52939 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52946 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-52948 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52954 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52958 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52963 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52970 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52972 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52975 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52981 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52982 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-52984 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52985 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52988 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52990 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52995 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-52999 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53001 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53003 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53012 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53015 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53017 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53018 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53021 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53037 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53039 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53047 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53050 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53056 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53060 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53061 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53063 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53064 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53065 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53066 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53073 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53074 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53076 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53077 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53080 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53082 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53083 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53086 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53093 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53107 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53111 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53122 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53128 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53134 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53135 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53139 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53146 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53147 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53150 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53158 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53159 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53167 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53168 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53177 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53181 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53199 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53208 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53213 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53218 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53219 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53220 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53221 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-53225 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53227 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53229 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53232 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53236 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53237 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53238 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53245 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53249 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53258 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53263 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53269 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53287 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53289 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53292 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53295 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53304 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53306 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53314 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53320 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53325 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53332 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53337 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53339 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53349 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53353 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53358 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-47432 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-50704 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50766 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-50815 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-23000 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52674 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52811 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53696 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53712 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53859 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53867 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54019 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54023 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54067 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54121 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54237 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54324 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27393 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-35865 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40092 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40094 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40099 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40100 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40103 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40219 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40253 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68173 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68206 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68321 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68778 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68780 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43030 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43194 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43211 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53088 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53284 | MEDIUM4.67 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | uuid-dev 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.2.11.dfsg-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-23914 | MEDIUM4.64 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-23914 | MEDIUM4.64 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | MEDIUM4.64 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58016 | MEDIUM4.64 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34000 | MEDIUM4.64 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34002 | MEDIUM4.64 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34000 | MEDIUM4.64 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34002 | MEDIUM4.64 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-9287 | MEDIUM4.64 | cipher-base 1.0.4 fixed in 1.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-42461 | MEDIUM4.64 | elliptic 6.5.4 fixed in 6.5.7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-48949 | MEDIUM4.64 | elliptic 6.5.4 fixed in 6.5.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33896 | MEDIUM4.64 | node-forge 1.3.0 fixed in 1.4.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33896 | MEDIUM4.64 | node-forge 1.3.1 fixed in 1.4.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9288 | MEDIUM4.64 | sha.js 2.4.11 fixed in 2.4.12 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-41079 | MEDIUM4.59 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.43.0-1+deb11u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-3530 | MEDIUM4.5 | binutils 2.35.2-2 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3530 | MEDIUM4.5 | binutils-common 2.35.2-2 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3530 | MEDIUM4.5 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-42916 | MEDIUM4.5 | curl 7.74.0-1.3+deb11u16 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | MEDIUM4.5 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | MEDIUM4.5 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | MEDIUM4.5 | libc-devtools 2.31-13+deb11u13 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | MEDIUM4.5 | libc-devtools 2.31-13+deb11u13 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-42916 | MEDIUM4.5 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-30581 | MEDIUM4.5 | nodejs 24.14.1-1nodesource1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48933 | MEDIUM4.5 | nodejs 24.14.1-1nodesource1 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3807 | MEDIUM4.5 | ansi-regex 3.0.0 fixed in 6.0.1, 5.0.1, 4.1.1, 3.0.1 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4068 | MEDIUM4.5 | braces 2.3.2 fixed in 3.0.3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4068 | MEDIUM4.5 | braces 3.0.2 fixed in 3.0.3 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2022-21676 | MEDIUM4.5 | engine.io 5.0.0 fixed in 4.1.2, 5.2.1, 6.1.1 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-43646 | MEDIUM4.5 | get-func-name 2.0.0 fixed in 2.0.1 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25881 | MEDIUM4.5 | http-cache-semantics 3.8.1 fixed in 4.1.1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-21536 | MEDIUM4.5 | http-proxy-middleware 2.0.4 fixed in 2.0.7, 3.0.3 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25851 | MEDIUM4.5 | jpeg-js 0.4.3 fixed in 0.4.4 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-37599 | MEDIUM4.5 | loader-utils 1.4.0 fixed in 1.4.2, 2.0.4, 3.2.1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-37603 | MEDIUM4.5 | loader-utils 1.4.0 fixed in 1.4.2, 2.0.4, 3.2.1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3517 | MEDIUM4.5 | minimatch 3.0.4 fixed in 3.0.5 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3803 | MEDIUM4.5 | nth-check 1.0.2 fixed in 2.0.1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25883 | MEDIUM4.5 | semver 5.7.1 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25883 | MEDIUM4.5 | semver 7.3.2 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25883 | MEDIUM4.5 | semver 7.3.5 fixed in 7.5.2, 6.3.1, 5.7.2 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0355 | MEDIUM4.5 | simple-get 3.1.0 fixed in 4.0.1, 3.1.1, 2.8.2 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-32695 | MEDIUM4.5 | socket.io-parser 4.0.5 fixed in 4.2.3, 3.4.3, 3.3.4 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-12905 | MEDIUM4.5 | tar-fs 2.1.1 fixed in 1.16.4, 2.1.2, 3.0.7 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-25858 | MEDIUM4.5 | terser 4.8.0 fixed in 4.8.1, 5.14.2 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-29180 | MEDIUM4.5 | webpack-dev-middleware 5.3.1 fixed in 7.1.0, 6.1.2, 5.3.4 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-5+deb11u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-5+deb11u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-5+deb11u3 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6-dev 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6-dev 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | MEDIUM4.5 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.1-5+deb11u9 fixed in 3.7.1-5+deb11u10 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 2.7.4-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount-dev 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount-dev 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libnss-systemd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libnss-systemd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libnss-systemd 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng-dev 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32907 | MEDIUM4.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1467 | MEDIUM4.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1536 | MEDIUM4.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1760 | MEDIUM4.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2443 | MEDIUM4.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2708 | MEDIUM4.5 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32907 | MEDIUM4.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1467 | MEDIUM4.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1536 | MEDIUM4.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1760 | MEDIUM4.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2443 | MEDIUM4.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2708 | MEDIUM4.5 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-3523 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-50700 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32255 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26886 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23457 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53194 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54181 | MEDIUM4.5 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | uuid-dev 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | uuid-dev 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-19726 | MEDIUM4.49 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-19726 | MEDIUM4.49 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2020-19726 | MEDIUM4.49 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-45133 | MEDIUM4.49 | @babel/traverse 7.22.8 fixed in 7.23.2, 8.0.0-alpha.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6951 | MEDIUM4.49 | simple-git 3.16.0 fixed in 3.36.0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-6734 | MEDIUM4.49 | undici 7.25.0 fixed in 7.28.0, 8.2.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12816 | MEDIUM4.44 | node-forge 1.3.0 fixed in 1.3.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-12816 | MEDIUM4.44 | node-forge 1.3.1 fixed in 1.3.2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34990 | MEDIUM4.42 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40343 | MEDIUM4.42 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | MEDIUM4.39 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58014 | MEDIUM4.39 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-55602 | MEDIUM4.39 | http-proxy-middleware 2.0.4 fixed in 3.0.6, 4.1.0, 2.0.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-55602 | MEDIUM4.39 | http-proxy-middleware 2.0.9 fixed in 3.0.6, 4.1.0, 2.0.10 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-23358 | MEDIUM4.32 | underscore 1.6.0 fixed in 1.12.1 | 4.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.26 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | — | Post-Exploit |
| CVE-2026-16118 | MEDIUM4.26 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | — | Post-Exploit |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.18.3-6+deb11u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng-dev 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM4.25 | libssl1.1 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52633 | MEDIUM4.25 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-55200 | MEDIUM4.23 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-52011 | MEDIUM4.23 | launch-editor 2.2.1 fixed in 2.9.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-52011 | MEDIUM4.23 | launch-editor 2.3.0 fixed in 2.9.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-52011 | MEDIUM4.23 | launch-editor 2.6.0 fixed in 2.9.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-12548 | MEDIUM4.2 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-12548 | MEDIUM4.2 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.18 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | MEDIUM4.18 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | MEDIUM4.18 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58010 | MEDIUM4.18 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58012 | MEDIUM4.18 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58013 | MEDIUM4.18 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-44705 | MEDIUM4.18 | tmp 0.0.33 fixed in 0.2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-44705 | MEDIUM4.18 | tmp 0.2.5 fixed in 0.2.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | MEDIUM4.13 | libc-dev-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | MEDIUM4.13 | libc-devtools 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-6545 | MEDIUM4.13 | pbkdf2 3.1.1 fixed in 3.1.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6547 | MEDIUM4.13 | pbkdf2 3.1.1 fixed in 3.1.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9277 | MEDIUM4.13 | shell-quote 1.8.1 fixed in 1.8.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-9277 | MEDIUM4.13 | shell-quote 1.8.3 fixed in 1.8.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28291 | MEDIUM4.13 | simple-git 3.16.0 fixed in 3.32.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2021-32819 | MEDIUM4.12 | squirrelly 7.9.2 fixed in 9.0.0 | 59.8% Actively Exploited | Post-Exploit |
| CVE-2025-60018 | MEDIUM4.08 | glib-networking 2.66.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60018 | MEDIUM4.08 | glib-networking-common 2.66.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60018 | MEDIUM4.08 | glib-networking-services 2.66.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libasan6 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libatomic1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libcc1-0 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-10-dev 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgcc-s1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libgomp1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libitm1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | liblsan0 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.9-stdlib 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libquadmath0 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0716 | MEDIUM4.08 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12549 | MEDIUM4.08 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6324 | MEDIUM4.08 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-0716 | MEDIUM4.08 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12549 | MEDIUM4.08 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6324 | MEDIUM4.08 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++-10-dev 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libstdc++6 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libtsan0 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | MEDIUM4.08 | libubsan1 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2019-8457 | MEDIUM4.06 | libdb5.3 5.3.28+dfsg1-0.8 No fix yet | 45.4% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1 0.183-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.4-2 2.4.57+dfsg-3+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount-dev 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-47382 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-47599 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27672 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-48751 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-48816 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-49201 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49215 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49443 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49579 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49588 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49630 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49632 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49967 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-50350 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52589 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52608 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52639 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53178 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53401 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53520 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53794 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53816 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54201 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54287 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24855 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26583 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26585 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26607 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27415 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36952 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-37354 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38580 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39500 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42253 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43866 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-47660 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47668 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49859 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53088 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53100 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21701 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22060 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37920 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38232 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40016 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40252 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68239 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71274 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23126 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23212 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23452 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23463 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31393 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31466 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31523 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31728 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31751 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43047 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43163 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43275 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43342 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43383 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43420 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43430 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43439 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43448 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45905 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52955 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53108 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53352 | MEDIUM4 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-54035 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54185 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54202 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26915 | MEDIUM4 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | uuid-dev 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2022-3715 | LOW3.98 | bash 5.1-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-45703 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47673 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47695 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47696 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1579 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-45703 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47673 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47695 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47696 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1579 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-44840 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-45703 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47673 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47695 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-47696 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1579 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW3.98 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2017-15131 | LOW3.98 | xdg-user-dirs 0.17-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33999 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34001 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34003 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50256 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50257 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50258 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50259 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50260 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50261 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50264 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55999 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56000 | LOW3.98 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33999 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34001 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34003 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50256 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50257 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50258 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50259 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50260 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50261 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50264 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-55999 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56000 | LOW3.98 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44728 | LOW3.98 | @babel/plugin-transform-modules-systemjs 7.22.5 fixed in 7.29.4, 8.0.0-alpha.13 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-44728 | LOW3.98 | @babel/plugin-transform-modules-systemjs 7.23.0 fixed in 7.29.4, 8.0.0-alpha.13 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-49934 | LOW3.91 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.35.2-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.35.2-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils-common 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-3826 | LOW3.9 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | curl 7.74.0-1.3+deb11u16 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | curl 7.74.0-1.3+deb11u16 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22922 | LOW3.9 | curl 7.74.0-1.3+deb11u16 No fix yet | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-9681 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-11856 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22922 | LOW3.9 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-6129 | LOW3.9 | libpng-tools 1.6.37-3+deb11u3 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3553 | LOW3.9 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-3553 | LOW3.9 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-39244 | LOW3.9 | adm-zip 0.5.10 fixed in 0.6.0 | — | Post-Exploit |
| CVE-2022-41940 | LOW3.9 | engine.io 5.0.0 fixed in 3.6.1, 6.2.1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28849 | LOW3.9 | follow-redirects 1.15.2 fixed in 1.15.6 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2021-46174 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-46174 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2021-46174 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.10-4+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW3.82 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW3.82 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58011 | LOW3.82 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58015 | LOW3.82 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-55199 | LOW3.82 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-59466 | LOW3.82 | nodejs 24.14.1-1nodesource1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48615 | LOW3.82 | nodejs 24.14.1-1nodesource1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48619 | LOW3.82 | nodejs 24.14.1-1nodesource1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.9 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.9 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-59892 | LOW3.82 | @opentelemetry/propagator-jaeger 1.12.0 fixed in 2.9.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34601 | LOW3.82 | @xmldom/xmldom 0.8.10 fixed in 0.8.12, 0.9.9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41672 | LOW3.82 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41673 | LOW3.82 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-41674 | LOW3.82 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41675 | LOW3.82 | @xmldom/xmldom 0.8.10 fixed in 0.8.13, 0.9.10 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69873 | LOW3.82 | ajv 6.12.6 fixed in 8.18.0, 6.14.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69873 | LOW3.82 | ajv 8.12.0 fixed in 8.18.0, 6.14.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-45590 | LOW3.82 | body-parser 1.19.2 fixed in 1.20.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW3.82 | brace-expansion 1.1.11 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33750 | LOW3.82 | brace-expansion 1.1.11 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW3.82 | brace-expansion 1.1.14 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW3.82 | brace-expansion 2.1.0 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-46234 | LOW3.82 | browserify-sign 4.2.1 fixed in 4.2.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-24001 | LOW3.82 | diff 3.5.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24001 | LOW3.82 | diff 4.0.2 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-24001 | LOW3.82 | diff 7.0.0 fixed in 8.0.3, 5.2.2, 4.0.4, 3.5.1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59725 | LOW3.82 | engine.io 5.0.0 fixed in 6.6.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59725 | LOW3.82 | engine.io 6.4.2 fixed in 6.6.7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13676 | LOW3.82 | fast-uri 3.1.0 fixed in 4.0.1, 3.1.3, 2.4.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6321 | LOW3.82 | fast-uri 3.1.0 fixed in 3.1.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6322 | LOW3.82 | fast-uri 3.1.0 fixed in 3.1.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12143 | LOW3.82 | form-data 2.3.3 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12143 | LOW3.82 | form-data 4.0.5 fixed in 2.5.6, 3.0.5, 4.0.6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59879 | LOW3.82 | immutable 4.3.8 fixed in 4.3.9, 5.1.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59880 | LOW3.82 | immutable 4.3.8 fixed in 4.3.9, 5.1.8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59869 | LOW3.82 | js-yaml 3.13.1 fixed in 3.15.0, 4.3.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59869 | LOW3.82 | js-yaml 3.14.1 fixed in 3.15.0, 4.3.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59869 | LOW3.82 | js-yaml 3.14.2 fixed in 3.15.0, 4.3.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59869 | LOW3.82 | js-yaml 4.1.1 fixed in 3.15.0, 4.3.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-26996 | LOW3.82 | minimatch 3.0.4 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-26996 | LOW3.82 | minimatch 3.0.5 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-26996 | LOW3.82 | minimatch 3.1.2 fixed in 10.2.1, 9.0.6, 8.0.5, 7.4.7, 6.2.1, 5.1.7, 4.2.4, 3.1.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66031 | LOW3.82 | node-forge 1.3.0 fixed in 1.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33891 | LOW3.82 | node-forge 1.3.0 fixed in 1.4.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33894 | LOW3.82 | node-forge 1.3.0 fixed in 1.4.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33895 | LOW3.82 | node-forge 1.3.0 fixed in 1.4.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66031 | LOW3.82 | node-forge 1.3.1 fixed in 1.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33891 | LOW3.82 | node-forge 1.3.1 fixed in 1.4.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33894 | LOW3.82 | node-forge 1.3.1 fixed in 1.4.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33895 | LOW3.82 | node-forge 1.3.1 fixed in 1.4.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15284 | LOW3.82 | qs 6.10.5 fixed in 6.14.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-2391 | LOW3.82 | qs 6.10.5 fixed in 6.14.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15284 | LOW3.82 | qs 6.11.2 fixed in 6.14.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-2391 | LOW3.82 | qs 6.11.2 fixed in 6.14.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15284 | LOW3.82 | qs 6.9.7 fixed in 6.14.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-2391 | LOW3.82 | qs 6.9.7 fixed in 6.14.2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34043 | LOW3.82 | serialize-javascript 6.0.1 fixed in 7.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34043 | LOW3.82 | serialize-javascript 6.0.2 fixed in 7.0.5 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33151 | LOW3.82 | socket.io-parser 4.0.5 fixed in 3.3.5, 3.4.4, 4.2.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-59343 | LOW3.82 | tar-fs 2.1.1 fixed in 3.1.1, 2.1.4, 1.16.6 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12151 | LOW3.82 | undici 7.25.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41907 | LOW3.82 | uuid 3.4.0 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41907 | LOW3.82 | uuid 8.3.2 fixed in 11.1.1, 12.0.1, 13.0.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48779 | LOW3.82 | ws 7.4.5 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48779 | LOW3.82 | ws 7.5.7 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-48779 | LOW3.82 | ws 8.11.0 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45736 | LOW3.82 | ws 8.11.0 fixed in 8.20.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-48779 | LOW3.82 | ws 8.13.0 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45736 | LOW3.82 | ws 8.13.0 fixed in 8.20.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-48779 | LOW3.82 | ws 8.18.3 fixed in 5.2.5, 6.2.4, 7.5.11, 8.21.0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-45736 | LOW3.82 | ws 8.18.3 fixed in 8.20.1 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4316 | LOW3.82 | zod 3.20.3 fixed in 3.22.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW3.82 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9697 | LOW3.77 | undici 7.25.0 fixed in 7.28.0, 8.5.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34757 | LOW3.74 | libpng-dev 1.6.37-3+deb11u3 fixed in 1.6.37-3+deb11u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34757 | LOW3.74 | libpng16-16 1.6.37-3+deb11u3 fixed in 1.6.37-3+deb11u4 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-47484 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-49196 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53733 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38540 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42123 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42230 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-50720 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26769 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40123 | LOW3.74 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23458 | LOW3.74 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-48387 | LOW3.72 | tar-fs 2.1.1 fixed in 1.16.5, 2.1.3, 3.0.9 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2020-13529 | LOW3.66 | systemd-sysv 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2020-13529 | LOW3.66 | systemd-timesyncd 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-10028 | LOW3.65 | glib-networking 2.66.0-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10028 | LOW3.65 | glib-networking-common 2.66.0-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10028 | LOW3.65 | glib-networking-services 2.66.0-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | libnss3 2:3.61-1+deb11u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4035 | LOW3.65 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4035 | LOW3.65 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3549 | LOW3.62 | binutils 2.35.2-2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-25584 | LOW3.62 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3549 | LOW3.62 | binutils-common 2.35.2-2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-25584 | LOW3.62 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-3549 | LOW3.62 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2023-25584 | LOW3.62 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6965 | LOW3.61 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 73.5% Actively Exploited | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1+deb11u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5574 | LOW3.57 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-5574 | LOW3.57 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW3.57 | libc-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8058 | LOW3.57 | libc6-dev 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28320 | LOW3.54 | curl 7.74.0-1.3+deb11u16 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4806 | LOW3.54 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4813 | LOW3.54 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4806 | LOW3.54 | libc-devtools 2.31-13+deb11u13 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-4813 | LOW3.54 | libc-devtools 2.31-13+deb11u13 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28320 | LOW3.54 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28176 | LOW3.54 | jose 4.11.2 fixed in 4.15.5, 2.0.7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37890 | LOW3.54 | ws 7.4.5 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37890 | LOW3.54 | ws 7.5.7 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37890 | LOW3.54 | ws 8.11.0 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-37890 | LOW3.54 | ws 8.13.0 fixed in 5.2.4, 6.2.3, 7.5.10, 8.17.1 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2016-1585 | LOW3.53 | libapparmor1 2.13.6-10 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-devtools 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-32002 | LOW3.53 | nodejs 24.14.1-1nodesource1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.11.dfsg-2+deb11u2 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g-dev 1:1.2.11.dfsg-2+deb11u2 No fix yet | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2022-37601 | LOW3.53 | loader-utils 1.4.0 fixed in 2.0.3, 1.4.1 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4800 | LOW3.53 | lodash 4.17.21 fixed in 4.18.0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2021-44906 | LOW3.53 | minimist 0.0.8 fixed in 1.2.6, 0.2.4 | 4.6% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-48646 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36928 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | libelf1 0.183-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23003 | LOW3.4 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12547 | LOW3.4 | libsoup-gnome2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2026-12547 | LOW3.4 | libsoup2.4-1 2.72.0-2+deb11u3 No fix yet | — | Directly Exposed |
| CVE-2024-53589 | LOW3.37 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-7598 | LOW3.36 | minimist 0.0.8 fixed in 0.2.1, 1.2.3 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.35.2-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.35.2-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 8.32-4+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW3.31 | libc-devtools 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-23915 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1 1.9.0-2+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW3.31 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-48618 | LOW3.31 | nodejs 24.14.1-1nodesource1 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.32.1-4+deb11u5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27904 | LOW3.31 | minimatch 3.0.4 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27904 | LOW3.31 | minimatch 3.0.5 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27904 | LOW3.31 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW3.31 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13311 | LOW3.31 | shell-quote 1.8.1 fixed in 1.9.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13311 | LOW3.31 | shell-quote 1.8.3 fixed in 1.9.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30360 | LOW3.31 | webpack-dev-server 4.15.1 fixed in 5.2.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6402 | LOW3.31 | webpack-dev-server 4.15.1 fixed in 5.2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6402 | LOW3.31 | webpack-dev-server 5.2.2 fixed in 5.2.4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.35.2-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.35.2-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20284 | LOW3.3 | binutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.35.2-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.35.2-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-common 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20284 | LOW3.3 | binutils-common 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010204 | LOW3.3 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20284 | LOW3.3 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35448 | LOW3.3 | libbinutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35448 | LOW3.3 | libctf-nobfd0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2020-35448 | LOW3.3 | libctf0 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-13221 | LOW3.28 | libperl5.32 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.74.0-1.3+deb11u16 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-7783 | LOW3.24 | form-data 2.3.3 fixed in 2.5.4, 3.0.4, 4.0.4 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-11831 | LOW3.24 | serialize-javascript 6.0.1 fixed in 6.0.2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-20197 | LOW3.21 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-20197 | LOW3.21 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-20197 | LOW3.21 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.7-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | curl 7.74.0-1.3+deb11u16 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22923 | LOW3.18 | curl 7.74.0-1.3+deb11u16 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010024 | LOW3.18 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW3.18 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010024 | LOW3.18 | libc-devtools 2.31-13+deb11u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW3.18 | libc-devtools 2.31-13+deb11u13 No fix yet | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2021-22923 | LOW3.18 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-16768 | LOW3.18 | libgdk-pixbuf2.0-bin 2.42.2+dfsg-1+deb11u5 No fix yet | — | Post-Exploit |
| CVE-2026-15588 | LOW3.18 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | — | Post-Exploit |
| CVE-2026-15588 | LOW3.18 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | — | Post-Exploit |
| CVE-2017-16137 | LOW3.18 | debug 3.2.6 fixed in 2.6.9, 3.1.0, 3.2.7, 4.3.1 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2017-16137 | LOW3.18 | debug 4.1.1 fixed in 2.6.9, 3.1.0, 3.2.7, 4.3.1 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2022-33987 | LOW3.18 | got 8.3.2 fixed in 12.1.0, 11.8.5 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2021-23362 | LOW3.18 | hosted-git-info 2.8.8 fixed in 2.8.9, 3.0.8 | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13465 | LOW3.18 | lodash 4.17.21 fixed in 4.17.23 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4067 | LOW3.18 | micromatch 3.1.10 fixed in 4.0.8 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4067 | LOW3.18 | micromatch 4.0.4 fixed in 4.0.8 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4067 | LOW3.18 | micromatch 4.0.5 fixed in 4.0.8 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2021-32640 | LOW3.18 | ws 7.4.5 fixed in 7.4.6, 6.2.2, 5.2.3 | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0842 | LOW3.18 | xml2js 0.4.23 fixed in 0.5.0 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.31-13+deb11u13 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2014-8166 | LOW3.17 | libcups2 2.3.3op2-3+deb11u10 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-8805 | LOW3.17 | linux-libc-dev 5.10.251-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-28162 | LOW3.16 | libpng-tools 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-60019 | LOW3.15 | glib-networking 2.66.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60019 | LOW3.15 | glib-networking-common 2.66.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60019 | LOW3.15 | glib-networking-services 2.66.0-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.10+dfsg-6.7+deb11u9 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-32251 | LOW3.15 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-29041 | LOW3.11 | express 4.17.3 fixed in 4.19.2, 5.0.0-beta.3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2023-26159 | LOW3.11 | follow-redirects 1.15.2 fixed in 1.15.4 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-41305 | LOW3.11 | postcss 8.4.31 fixed in 8.5.10 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-43788 | LOW3.11 | webpack 5.88.2 fixed in 5.94.0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-35737 | LOW3.1 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 18.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15281 | LOW3.01 | libc-dev-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5435 | LOW3.01 | libc-devtools 2.31-13+deb11u13 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15281 | LOW3.01 | libc-devtools 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-21717 | LOW3.01 | nodejs 24.14.1-1nodesource1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12590 | LOW3.01 | body-parser 1.19.2 fixed in 1.20.6, 2.3.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12590 | LOW3.01 | body-parser 1.20.4 fixed in 1.20.6, 2.3.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27903 | LOW3.01 | minimatch 3.0.4 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27903 | LOW3.01 | minimatch 3.0.5 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27903 | LOW3.01 | minimatch 3.1.2 fixed in 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, 3.1.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27601 | LOW3.01 | underscore 1.6.0 fixed in 1.13.8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9678 | LOW3.01 | undici 7.25.0 fixed in 7.28.0, 8.5.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9679 | LOW3.01 | undici 7.25.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-30359 | LOW3.01 | webpack-dev-server 4.15.1 fixed in 5.2.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2012-0039 | LOW3 | libglib2.0-bin 2.66.8-1+deb11u8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2012-0039 | LOW3 | libglib2.0-dev-bin 2.66.8-1+deb11u8 No fix yet | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12318 | LOW2.89 | libnss3 2:3.61-1+deb11u5 fixed in 2:3.61-1+deb11u6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-14505 | LOW2.86 | elliptic 6.5.4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-35205 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-35206 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48063 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-48065 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-25585 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25586 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-25588 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-35205 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-35206 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48063 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-48065 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-25585 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25586 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-25588 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2021-46195 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2022-35205 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-35206 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-38533 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-4285 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47007 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47008 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47010 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-47011 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-48063 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-48064 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2022-48065 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-25585 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-25586 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-25588 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-4214 | LOW2.8 | libpng-tools 1.6.37-3+deb11u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-15853 | LOW2.8 | x11-xkb-utils 7.7+5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-15859 | LOW2.8 | x11-xkb-utils 7.7+5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-15861 | LOW2.8 | x11-xkb-utils 7.7+5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-15863 | LOW2.8 | x11-xkb-utils 7.7+5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-50262 | LOW2.8 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50263 | LOW2.8 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50262 | LOW2.8 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-50263 | LOW2.8 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.16.0-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libnss-systemd 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libnss-systemd 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.9-stdlib 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.9-stdlib 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.9-stdlib 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.10+dfsg-6.7+deb11u9 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-1075 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52561 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52926 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53992 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54145 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54153 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41027 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-47738 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40341 | LOW2.8 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31668 | LOW2.8 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48928 | LOW2.75 | nodejs 24.14.1-1nodesource1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0915 | LOW2.7 | libc-dev-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc-dev-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0915 | LOW2.7 | libc-devtools 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-4046 | LOW2.7 | libc-devtools 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3713 | LOW2.7 | libpng-tools 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-31437 | LOW2.7 | systemd-sysv 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31438 | LOW2.7 | systemd-sysv 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31439 | LOW2.7 | systemd-sysv 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-31437 | LOW2.7 | systemd-timesyncd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31438 | LOW2.7 | systemd-timesyncd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-31439 | LOW2.7 | systemd-timesyncd 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.2.5-2.1~deb11u1 fixed in 5.2.5-2.1~deb11u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-54285 | LOW2.7 | @opentelemetry/core 1.12.0 fixed in 2.8.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2739 | LOW2.7 | bn.js 4.12.0 fixed in 4.12.3, 5.2.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-2739 | LOW2.7 | bn.js 5.2.0 fixed in 4.12.3, 5.2.3 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-42459 | LOW2.7 | elliptic 6.5.4 fixed in 6.5.7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-42460 | LOW2.7 | elliptic 6.5.4 fixed in 6.5.7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-32996 | LOW2.7 | http-proxy-middleware 2.0.4 fixed in 2.0.8, 3.0.4 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-32997 | LOW2.7 | http-proxy-middleware 2.0.4 fixed in 2.0.9, 3.0.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-64718 | LOW2.7 | js-yaml 3.13.1 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53550 | LOW2.7 | js-yaml 3.13.1 fixed in 4.2.0, 3.15.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-64718 | LOW2.7 | js-yaml 3.14.1 fixed in 4.1.1, 3.14.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53550 | LOW2.7 | js-yaml 3.14.1 fixed in 4.2.0, 3.15.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53550 | LOW2.7 | js-yaml 3.14.2 fixed in 4.2.0, 3.15.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53550 | LOW2.7 | js-yaml 4.1.1 fixed in 4.2.0, 3.15.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53632 | LOW2.7 | launch-editor 2.12.0 fixed in 2.14.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53632 | LOW2.7 | launch-editor 2.2.1 fixed in 2.14.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53632 | LOW2.7 | launch-editor 2.3.0 fixed in 2.14.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53632 | LOW2.7 | launch-editor 2.6.0 fixed in 2.14.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-2950 | LOW2.7 | lodash 4.17.21 fixed in 4.18.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-57352 | LOW2.7 | min-document 2.19.0 fixed in 2.19.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5078 | LOW2.7 | morgan 1.9.1 fixed in 1.11.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66030 | LOW2.7 | node-forge 1.3.0 fixed in 1.3.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66030 | LOW2.7 | node-forge 1.3.1 fixed in 1.3.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-45296 | LOW2.7 | path-to-regexp 0.1.7 fixed in 1.9.0, 0.1.10, 8.0.0, 3.3.0, 6.3.0 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-52798 | LOW2.7 | path-to-regexp 0.1.7 fixed in 0.1.12 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-4867 | LOW2.7 | path-to-regexp 0.1.7 fixed in 0.1.13 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW2.7 | picomatch 2.3.1 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-54798 | LOW2.7 | tmp 0.0.33 fixed in 0.2.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-7608 | LOW2.7 | yargs-parser 13.1.1 fixed in 13.1.2, 15.0.1, 18.1.1, 5.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.64 | coreutils 8.32-4+b1 No fix yet | — | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.34-4+deb11u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | LOW2.55 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5450 | LOW2.55 | libc-devtools 2.31-13+deb11u13 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5928 | LOW2.55 | libc-devtools 2.31-13+deb11u13 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-28164 | LOW2.55 | libpng-tools 1.6.37-3+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW2.55 | openssl 1.1.1w-0+deb11u5 fixed in 1.1.1w-0+deb11u8 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.10+dfsg-6.7+deb11u9 fixed in 2.9.10+dfsg-6.7+deb11u10 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-4039 | LOW2.45 | cpp-10 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | g++-10 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-10 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-10-base 10.2.1-6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-4039 | LOW2.45 | gcc-9-base 9.3.0-22 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.9 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 8.32-4+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.10-4+deb11u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | login 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2013-4235 | LOW2.4 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.36.1-8+deb11u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-43796 | LOW2.4 | express 4.17.3 fixed in 4.20.0, 5.0.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-43799 | LOW2.4 | send 0.17.1 fixed in 0.19.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-43799 | LOW2.4 | send 0.17.2 fixed in 0.19.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-43800 | LOW2.4 | serve-static 1.14.2 fixed in 1.16.0, 2.1.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-14620 | LOW2.4 | webpack-dev-server 4.15.1 fixed in 5.2.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-14620 | LOW2.4 | webpack-dev-server 5.2.2 fixed in 5.2.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.74.0-1.3+deb11u16 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4756 | LOW2.4 | libc-dev-bin 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4756 | LOW2.4 | libc-devtools 2.31-13+deb11u13 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW2.29 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW2.29 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-5642 | LOW2.29 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils 8.32-4+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-34757 | LOW2.24 | libpng-tools 1.6.37-3+deb11u3 fixed in 1.6.37-3+deb11u4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-21538 | LOW2.24 | cross-spawn 6.0.5 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2024-21538 | LOW2.24 | cross-spawn 7.0.3 fixed in 7.0.5, 6.0.6 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt-transport-https 2.2.4 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48934 | LOW2.19 | nodejs 24.14.1-1nodesource1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-14631 | LOW2.19 | webpack-dev-server 4.15.1 fixed in 5.2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9595 | LOW2.19 | webpack-dev-server 4.15.1 fixed in 5.2.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-14631 | LOW2.19 | webpack-dev-server 5.2.2 fixed in 5.2.6 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9595 | LOW2.19 | webpack-dev-server 5.2.2 fixed in 5.2.5 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW2.14 | libc-dev-bin 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8058 | LOW2.14 | libc-devtools 2.31-13+deb11u13 fixed in 2.31-13+deb11u14 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff5 4.2.0-1+deb11u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-35448 | LOW1.98 | binutils 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35448 | LOW1.98 | binutils-common 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-35448 | LOW1.98 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48931 | LOW1.89 | nodejs 24.14.1-1nodesource1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-47764 | LOW1.89 | cookie 0.4.0 fixed in 0.7.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-47764 | LOW1.89 | cookie 0.4.2 fixed in 0.7.0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-48948 | LOW1.89 | elliptic 6.5.4 fixed in 6.6.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11525 | LOW1.89 | undici 7.25.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6733 | LOW1.89 | undici 7.25.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68157 | LOW1.89 | webpack 5.88.2 fixed in 5.104.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68458 | LOW1.89 | webpack 5.88.2 fixed in 5.104.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.8.1-1+deb11u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-49356 | LOW1.84 | @babel/core 7.22.9 fixed in 8.0.0-rc.6, 7.29.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-49356 | LOW1.84 | @babel/core 7.23.2 fixed in 8.0.0-rc.6, 7.29.6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7339 | LOW1.73 | on-headers 1.0.2 fixed in 1.1.0 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48935 | LOW1.68 | nodejs 24.14.1-1nodesource1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.9 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.9 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.9 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.9-minimal 3.9.2-1+deb11u6 fixed in 3.9.2-1+deb11u7 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW1.68 | systemd-sysv 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW1.68 | systemd-sysv 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW1.68 | systemd-timesyncd 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW1.68 | systemd-timesyncd 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-5889 | LOW1.58 | brace-expansion 1.1.11 fixed in 2.0.2, 1.1.12, 3.0.1, 4.0.1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.35.2-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2024-5642 | LOW1.38 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2020-13529 | NONE0 | libpam-systemd 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-13529 | NONE0 | systemd 247.3-7+deb11u8 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-31437 | NONE0 | libpam-systemd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libpam-systemd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libpam-systemd 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd 247.3-7+deb11u8 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd 247.3-7+deb11u8 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.27-2+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.27-2+deb11u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.4.0-9+deb11u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.27-2+deb11u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libpam-systemd 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libpam-systemd 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.2+20201114-2+deb11u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd 247.3-7+deb11u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 247.3-7+deb11u8 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.1-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-56391 | NONE0 | coreutils 8.32-4+b1 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | curl 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53910 | NONE0 | diffutils 1:3.7-5 No fix yet | — | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.20.13 fixed in 1.20.14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2 1.2.4-1.1+deb11u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.4-1.1+deb11u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid-dev 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-8458 | NONE0 | libcurl4 7.74.0-1.3+deb11u16 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | libdpkg-perl 1.20.13 fixed in 1.20.14 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56407 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.2.10-2+deb11u7 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm-dev 20.3.5-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm-dev 20.3.5-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm-dev 20.3.5-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm-dev 20.3.5-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 20.3.5-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 20.3.5-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 20.3.5-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 20.3.5-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl1 1.3.2-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgl1-mesa-dri 20.3.5-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 20.3.5-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 20.3.5-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 20.3.5-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | libglapi-mesa 20.3.5-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglapi-mesa 20.3.5-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglapi-mesa 20.3.5-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglapi-mesa 20.3.5-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.3.2-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 20.3.5-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 20.3.5-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 20.3.5-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 20.3.5-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx0 1.3.2-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-50593 | NONE0 | libgraphite2-3 1.3.14-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0772585-D41D8C | NONE0 | libjson-glib-1.0-0 1.6.2-1 No fix yet | — | Not Applicable |
| TEMP-0772585-D41D8C | NONE0 | libjson-glib-1.0-common 1.6.2-1 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.12~rc1-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount-dev 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount-dev 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-16389 | NONE0 | libnss3 2:3.61-1+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.32 5.32.1-4+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.32 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-40930 | NONE0 | libpng-dev 1.6.37-3+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40930 | NONE0 | libpng-tools 1.6.37-3+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-40930 | NONE0 | libpng16-16 1.6.37-3+deb11u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.9-stdlib 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.34.1-3+deb11u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66032 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-66033 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-66034 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-66035 | NONE0 | libssh2-1 1.9.0-2+deb11u1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl1.1 1.1.1w-0+deb11u5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff5 4.2.0-1+deb11u8 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-43011 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53215 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23372 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31405 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31656 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31657 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31659 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31780 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43206 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43236 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43370 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52914 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53040 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53043 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53068 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53130 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53186 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-50634 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-50708 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53699 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53707 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53742 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53748 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53834 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54020 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54047 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54151 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54157 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54180 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54182 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36331 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-27558 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40032 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40036 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40043 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40093 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40095 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40107 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40112 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40124 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40126 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40193 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40288 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40314 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40358 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68254 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68256 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68303 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68330 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68335 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68765 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68772 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68781 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71192 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23245 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31396 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31417 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31494 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31683 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31768 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43184 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43203 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43336 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43373 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45958 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46328 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52919 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52922 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52931 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-52934 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53041 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53045 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53329 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53356 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-53374 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-53375 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-53382 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63796 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63798 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63814 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63827 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63828 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63834 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63835 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63836 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63895 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63905 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63908 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63915 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63930 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63931 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63933 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63934 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63954 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-63960 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-63967 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64010 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64055 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64056 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64083 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64084 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64085 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64086 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64087 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64088 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64089 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64090 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64091 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64092 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64093 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64094 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64095 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64096 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64097 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64135 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64165 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64168 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64188 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-31761 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43207 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43232 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43283 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46250 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46265 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46270 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.257-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53161 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53216 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53217 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53273 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64218 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64219 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64221 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64222 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64225 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64227 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64234 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64237 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64242 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64245 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64249 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64252 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64396 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64523 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| CVE-2026-64528 | NONE0 | linux-libc-dev 5.10.251-1 fixed in 5.10.259-1 | — | Not Applicable |
| CVE-2026-64529 | NONE0 | linux-libc-dev 5.10.251-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2023-45913 | NONE0 | mesa-vulkan-drivers 20.3.5-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | mesa-vulkan-drivers 20.3.5-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | mesa-vulkan-drivers 20.3.5-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | mesa-vulkan-drivers 20.3.5-1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-56434 | NONE0 | nginx 1.23.0-1~bullseye No fix yet | — | Not Applicable |
| CVE-2026-60005 | NONE0 | nginx 1.23.0-1~bullseye No fix yet | — | Not Applicable |
| TEMP-1138794-BADE22 | NONE0 | nginx 1.23.0-1~bullseye No fix yet | — | Not Applicable |
| CVE-2026-48617 | NONE0 | nodejs 24.14.1-1nodesource1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-48937 | NONE0 | nodejs 24.14.1-1nodesource1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 1.1.1w-0+deb11u5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.8.1-1+deb11u1 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.32.1-4+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.32 5.32.1-4+deb11u5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.9 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-11940 | NONE0 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.9-minimal 3.9.2-1+deb11u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 2.96-7+deb11u1 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1+deb11u1 No fix yet | — | Not Applicable |
| DLA-4569-1 | NONE0 | tzdata 2025b-0+deb11u2 fixed in 2026b-0+deb11u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | uuid-dev 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | uuid-dev 2.36.1-8+deb11u2 No fix yet | — | Not Applicable |
| CVE-2022-49737 | NONE0 | xserver-common 2:1.20.11-1+deb11u17 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-49737 | NONE0 | xvfb 2:1.20.11-1+deb11u17 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-27789 | NONE0 | @babel/helpers 7.22.6 fixed in 7.26.10, 8.0.0-alpha.17 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-27789 | NONE0 | @babel/runtime 7.22.6 fixed in 7.26.10, 8.0.0-alpha.17 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-14257 | NONE0 | brace-expansion 1.1.11 fixed in 5.0.8 | — | Not Applicable |
| CVE-2026-14257 | NONE0 | brace-expansion 1.1.14 fixed in 5.0.8 | — | Not Applicable |
| CVE-2026-14257 | NONE0 | brace-expansion 2.1.0 fixed in 5.0.8 | — | Not Applicable |
| GHSA-vjh7-7g9h-fjfh | NONE0 | elliptic 6.5.4 fixed in 6.6.1 | — | Not Applicable |
| CVE-2026-16221 | NONE0 | fast-uri 3.1.0 fixed in 2.4.3, 3.1.4, 4.1.1 | — | Not Applicable |
| GHSA-r4q5-vmmm-2653 | NONE0 | follow-redirects 1.15.2 fixed in 1.16.0 | — | Not Applicable |
| GHSA-6x33-pw7p-hmpq | NONE0 | http-proxy 1.18.0 fixed in 1.18.1 | — | Not Applicable |
| CVE-2024-36751 | NONE0 | parseuri 0.0.6 fixed in 2.0.0 | 0.5% Theoretical Threat | Not Applicable |
| GHSA-x565-32qp-m3vf | NONE0 | phin 2.9.3 fixed in 3.7.1 | — | Not Applicable |
| CVE-2026-45623 | NONE0 | postcss 8.4.31 fixed in 8.5.12 | — | Not Applicable |
| GHSA-r28c-9q8g-f849 | NONE0 | postcss 8.4.31 fixed in 8.5.18 | — | Not Applicable |
| CVE-2026-8723 | NONE0 | qs 6.11.2 fixed in 6.15.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8723 | NONE0 | qs 6.14.2 fixed in 6.15.2 | 0.4% Theoretical Threat | Not Applicable |
| GHSA-5c6j-r48x-rmvq | NONE0 | serialize-javascript 6.0.1 fixed in 7.0.3 | — | Not Applicable |
| GHSA-5c6j-r48x-rmvq | NONE0 | serialize-javascript 6.0.2 fixed in 7.0.3 | — | Not Applicable |
| GHSA-2p49-hgcm-8545 | NONE0 | svgo 3.3.3 fixed in 2.8.3, 3.3.4, 4.0.2 | — | Not Applicable |
| CVE-2026-54466 | NONE0 | websocket-driver 0.7.4 fixed in 0.7.5 | — | Not Applicable |
| CVE-2026-54490 | NONE0 | websocket-driver 0.7.4 fixed in 0.7.5 | — | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.