This base/runtime image ships critical vulnerabilities that any image built on it would inherit; they must be remediated before the final image goes to production. An attacker could execute arbitrary code (e.g., via heap overflows in aom or command injection in ImageMagick) leading to full system compromise. Note that CVE-2023-34152 requires ImageMagick's --enable-pipes configure option, which is non-default, reducing its exploitability in standard deployments. However, the overall vulnerability load demands immediate package updates or replacement of the base image. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-6879 | CRITICAL9.8 | libaom3 3.6.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34152 | CRITICAL9.8 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-45853 | CRITICAL9.8 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5841 | CRITICAL9.1 | libopenexr-3-1-30 3.1.5-5 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5841 | CRITICAL9.1 | libopenexr-dev 3.1.5-5 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | HIGH8.8 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2014-8166 | HIGH8.8 | libcups2 2.4.2-3+deb12u9 No fix yet | 3.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | HIGH8.8 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | HIGH8.8 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | HIGH8.8 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libegl-mesa0 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgbm1 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libgl1-mesa-dri 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libglapi-mesa 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40393 | HIGH8.33 | libglx-mesa0 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44170 | HIGH8.33 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH8.33 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44170 | HIGH8.33 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH8.33 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44170 | HIGH8.33 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH8.33 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42217 | HIGH8.33 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42217 | HIGH8.33 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44170 | HIGH8.33 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-44172 | HIGH8.33 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2008-4609 | HIGH8.16 | linux-libc-dev 6.1.174-1 No fix yet | 32.1% High Exploitation Risk | Directly Exposed |
| CVE-2023-31486 | HIGH8.1 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-34152 | HIGH7.84 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH7.84 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH7.84 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH7.84 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH7.84 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2023-34152 | HIGH7.84 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2013-7445 | HIGH7.8 | linux-libc-dev 6.1.174-1 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19449 | HIGH7.8 | linux-libc-dev 6.1.174-1 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19814 | HIGH7.8 | linux-libc-dev 6.1.174-1 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19378 | HIGH7.8 | linux-libc-dev 6.1.174-1 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-25265 | HIGH7.8 | linux-libc-dev 6.1.174-1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46470 | HIGH7.73 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42216 | HIGH7.73 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42216 | HIGH7.73 | libopenexr-dev 3.1.5-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2369 | HIGH7.73 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2369 | HIGH7.73 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-32911 | HIGH7.65 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32911 | HIGH7.65 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-25193 | HIGH7.5 | libharfbuzz-icu0 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-25193 | HIGH7.5 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libip4tc2 1.8.9-2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2020-36325 | HIGH7.5 | libjansson4 2.14-2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 4.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-19070 | HIGH7.5 | linux-libc-dev 6.1.174-1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0400 | HIGH7.5 | linux-libc-dev 6.1.174-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3083 | HIGH7.48 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3085 | HIGH7.48 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-32740 | HIGH7.48 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-49463 | HIGH7.48 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-20664 | HIGH7.48 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-28857 | HIGH7.48 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28859 | HIGH7.48 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41142 | HIGH7.48 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41142 | HIGH7.48 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-20664 | HIGH7.48 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-28857 | HIGH7.48 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-28859 | HIGH7.48 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0719 | HIGH7.31 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1761 | HIGH7.31 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-0719 | HIGH7.31 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1761 | HIGH7.31 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM6.97 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14523 | MEDIUM6.97 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2436 | MEDIUM6.97 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5119 | MEDIUM6.97 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14523 | MEDIUM6.97 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-2436 | MEDIUM6.97 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5119 | MEDIUM6.97 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39191 | MEDIUM6.97 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41071 | MEDIUM6.88 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmf-dev 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3996 | MEDIUM6.8 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11082 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11083 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5244 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-5245 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7545 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-7546 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6846 | MEDIUM6.63 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses5-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncurses6 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw5-dev 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | MEDIUM6.63 | libodbc1 2.3.11-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | MEDIUM6.63 | libodbc2 2.3.11-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-1013 | MEDIUM6.63 | libodbccr2 2.3.11-2+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12495 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12495 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12839 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12840 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27622 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34588 | MEDIUM6.63 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3847 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52452 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52624 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-52751 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53218 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-21803 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-26836 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26913 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26914 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26944 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35887 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38570 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38630 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41045 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-42118 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44941 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44942 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44951 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46729 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46811 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46813 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47691 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50029 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50217 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50226 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50282 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53068 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53168 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53179 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53218 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56538 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56775 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57900 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-58093 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21863 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21927 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21967 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21969 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23133 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37750 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37777 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37861 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-37952 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37957 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38069 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38117 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38182 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38206 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38248 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38349 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38369 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38582 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38584 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38585 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38595 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38627 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38722 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38734 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39797 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39810 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39859 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39952 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71068 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71073 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71152 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23171 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23208 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23226 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-23361 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23447 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23448 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31488 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31489 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31493 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31500 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31527 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31532 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31576 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31578 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31580 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31581 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31583 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31686 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31696 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31702 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31709 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31715 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31729 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43049 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43250 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45996 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46004 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46047 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46163 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46180 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46189 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46219 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46234 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46241 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46323 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46331 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46274 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-12456 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-11725 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-26934 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-3238 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-26242 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-3640 | MEDIUM6.63 | linux-libc-dev 6.1.174-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-44171 | MEDIUM6.63 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69720 | MEDIUM6.63 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-21759 | MEDIUM6.6 | linux-libc-dev 6.1.174-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libbinutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0856 | MEDIUM6.5 | libcaca0 0.99.beta20-3 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-gobject2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2-dev 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | MEDIUM6.5 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | MEDIUM6.5 | libcairo2-dev 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf-nobfd0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libctf0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20712 | MEDIUM6.5 | libgprofng0 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig-dev 2.1-6.1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11754 | MEDIUM6.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-11755 | MEDIUM6.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-15607 | MEDIUM6.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 5.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2004-0230 | MEDIUM6.5 | linux-libc-dev 6.1.174-1 No fix yet | 80.9% Actively Exploited | Directly Exposed |
| CVE-2026-53705 | MEDIUM6.46 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1940 | MEDIUM6.38 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39616 | MEDIUM6.38 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM6.38 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33164 | MEDIUM6.38 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libdw1 0.188-2.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.188-2.1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-0840 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1179 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-66864 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66866 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69649 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69650 | MEDIUM6.38 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-49218 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53460 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53461 | MEDIUM6.38 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-64181 | MEDIUM6.38 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34543 | MEDIUM6.38 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32906 | MEDIUM6.38 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32913 | MEDIUM6.38 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4948 | MEDIUM6.38 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4271 | MEDIUM6.38 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32049 | MEDIUM6.38 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-32906 | MEDIUM6.38 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32913 | MEDIUM6.38 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-4948 | MEDIUM6.38 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4271 | MEDIUM6.38 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-32049 | MEDIUM6.38 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-43501 | MEDIUM6.38 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46195 | MEDIUM6.38 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43110 | MEDIUM6.38 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22037 | MEDIUM6.32 | linux-libc-dev 6.1.174-1 No fix yet | 23.3% High Exploitation Risk | Directly Exposed |
| CVE-2025-32914 | MEDIUM6.29 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-32914 | MEDIUM6.29 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-40170 | MEDIUM6.29 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34544 | MEDIUM6.21 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34545 | MEDIUM6.21 | libopenexr-dev 3.1.5-5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3099 | MEDIUM6.21 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3099 | MEDIUM6.21 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31607 | MEDIUM6.21 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-53781 | MEDIUM6.21 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39981 | MEDIUM6.21 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43248 | MEDIUM6.21 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48163 | MEDIUM6.12 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48165 | MEDIUM6.12 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3442 | MEDIUM6.03 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68431 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32741 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32882 | MEDIUM6.03 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34379 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40244 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40250 | MEDIUM6.03 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM6.03 | libtheora0 1.1.1+dfsg.1-16.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26669 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41935 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53147 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57982 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21985 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22039 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22104 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38081 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38204 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38616 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38636 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39744 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39901 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23327 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31568 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43052 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45957 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45994 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46022 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46033 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46191 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-25742 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-25743 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36013 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-53216 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40064 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68183 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68324 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31613 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31685 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43126 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43414 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46053 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46056 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46120 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46135 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46150 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46209 | MEDIUM6.03 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13699 | MEDIUM5.95 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13699 | MEDIUM5.95 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13699 | MEDIUM5.95 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-3864 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-52586 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42162 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37776 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23191 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31419 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31663 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43125 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43198 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43494 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45852 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45858 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46054 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46090 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46099 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46116 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46125 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46181 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46227 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46319 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46330 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53762 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57984 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40158 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40168 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40328 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23050 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31586 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31694 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43116 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43303 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43491 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43493 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45840 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45859 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-45892 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45894 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45899 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45934 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45942 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46015 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46043 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46052 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46069 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46119 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46123 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46132 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46133 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-46149 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46173 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46185 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46242 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46266 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-46275 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46294 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46306 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46324 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-1247 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-2961 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45884 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-45885 | MEDIUM5.95 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13699 | MEDIUM5.95 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-1121 | MEDIUM5.9 | linux-libc-dev 6.1.174-1 No fix yet | 4.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-3714 | MEDIUM5.9 | linux-libc-dev 6.1.174-1 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-46421 | MEDIUM5.78 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-46421 | MEDIUM5.78 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM5.7 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-40897 | MEDIUM5.7 | liborc-0.4-0 1:0.4.33-2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2020-36694 | MEDIUM5.7 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-21264 | MEDIUM5.7 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53095 | MEDIUM5.7 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57795 | MEDIUM5.7 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21714 | MEDIUM5.7 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21739 | MEDIUM5.7 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | MEDIUM5.61 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45991 | MEDIUM5.61 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | MEDIUM5.52 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-32738 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32739 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-32814 | MEDIUM5.52 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-46299 | MEDIUM5.52 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48733 | MEDIUM5.52 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-53463 | MEDIUM5.52 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-21968 | MEDIUM5.52 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-21968 | MEDIUM5.52 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-21968 | MEDIUM5.52 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncurses-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncurses5-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncurses6 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncursesw5-dev 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.42.2-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-dev 0.42.2-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7774 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | MEDIUM5.52 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-2784 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-32052 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32053 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32910 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32912 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-46420 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4969 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-1801 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3633 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3634 | MEDIUM5.52 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-2784 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-32052 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32053 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32910 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32912 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-46420 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4969 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-1801 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3633 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3634 | MEDIUM5.52 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-46299 | MEDIUM5.52 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6240 | MEDIUM5.52 | linux-libc-dev 6.1.174-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-36968 | MEDIUM5.52 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31588 | MEDIUM5.52 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43239 | MEDIUM5.52 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-0564 | MEDIUM5.52 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-21968 | MEDIUM5.52 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | MEDIUM5.52 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2-dev 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-13716 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20673 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-9996 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2016-8678 | MEDIUM5.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7275 | MEDIUM5.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2193 | MEDIUM5.5 | linux-libc-dev 6.1.174-1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-40074 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23383 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31502 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31516 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-44032 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44033 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-44034 | MEDIUM5.44 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2574 | MEDIUM5.4 | glib-networking 2.74.0-4 No fix yet | — | Directly Exposed |
| CVE-2026-2574 | MEDIUM5.4 | glib-networking-common 2.74.0-4 No fix yet | — | Directly Exposed |
| CVE-2026-2574 | MEDIUM5.4 | glib-networking-services 2.74.0-4 No fix yet | — | Directly Exposed |
| CVE-2026-27447 | MEDIUM5.35 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-3397 | MEDIUM5.35 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40307 | MEDIUM5.35 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40918 | MEDIUM5.35 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.5.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2015-9019 | MEDIUM5.3 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39314 | MEDIUM5.27 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | MEDIUM5.27 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28162 | MEDIUM5.27 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2-dev 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40146 | MEDIUM5.27 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40071 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40355 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68342 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68736 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31449 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31505 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31700 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31708 | MEDIUM5.18 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-32570 | MEDIUM5.02 | libdav1d6 1.0.0-2+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48994 | MEDIUM5.02 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32050 | MEDIUM5.02 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9901 | MEDIUM5.02 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-32050 | MEDIUM5.02 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-9901 | MEDIUM5.02 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2-dev 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-bin 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-data 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-dev-bin 2.74.6-2+deb12u9 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2008-3134 | MEDIUM5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmf-dev 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3477 | MEDIUM5 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 4.9% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4563 | MEDIUM5 | linux-libc-dev 6.1.174-1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1539 | MEDIUM4.93 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1539 | MEDIUM4.93 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53706 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54107 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54141 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23239 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23240 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46065 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46113 | MEDIUM4.93 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-49569 | MEDIUM4.84 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46024 | MEDIUM4.84 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-23039 | MEDIUM4.84 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-47183 | MEDIUM4.76 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-0630 | MEDIUM4.7 | linux-libc-dev 6.1.174-1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-46469 | MEDIUM4.67 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libasan8 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libatomic1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libcc1-0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | MEDIUM4.67 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libdw1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgomp1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-11081 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11412 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11413 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11414 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11494 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11495 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11839 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11840 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-3198 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69651 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8224 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6844 | MEDIUM4.67 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libitm1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-26924 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-29932 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29933 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29934 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29935 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29939 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29941 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-29942 | MEDIUM4.67 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | liblsan0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-48734 | MEDIUM4.67 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2005-0406 | MEDIUM4.67 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-14988 | MEDIUM4.67 | libopenexr-3-1-30 3.1.5-5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-48074 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-14988 | MEDIUM4.67 | libopenexr-dev 3.1.5-5 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libquadmath0 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3632 | MEDIUM4.67 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3632 | MEDIUM4.67 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++-12-dev 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libtsan2 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libubsan1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40347 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-0597 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-23005 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31082 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-37454 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4133 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52485 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52590 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52591 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52625 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52629 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52648 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52671 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52676 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52761 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52770 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52797 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-52888 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52920 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53149 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53231 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53261 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53292 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53336 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53353 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53367 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53394 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53429 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53460 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53491 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53523 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53529 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53538 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53574 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-53627 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53846 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53989 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53999 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54013 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54271 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54280 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6039 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25740 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26670 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26677 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26691 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26740 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26756 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26799 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26841 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26866 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26876 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26902 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26947 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26948 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26953 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26962 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27010 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27011 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27012 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27041 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-27057 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27062 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27079 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35784 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35794 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35799 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35808 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35860 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35904 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35924 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35931 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35942 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35945 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35946 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35951 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35961 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36911 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36922 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36951 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38557 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38564 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38594 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38608 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38620 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38622 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-38625 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40965 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40969 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-40975 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40998 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-40999 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41008 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-41023 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41031 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-41082 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42128 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42139 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42239 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42241 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42243 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42279 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42317 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43819 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43824 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43850 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43872 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-43899 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43901 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-43913 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-44963 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-45015 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46678 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46681 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46698 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46727 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46728 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46730 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46754 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46760 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46765 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46775 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46776 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46806 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46808 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46834 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46860 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47141 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47658 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47661 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47662 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47664 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47703 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47752 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-47794 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49568 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49893 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49901 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49906 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49908 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49910 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49914 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49916 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49918 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49919 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49920 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49921 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49922 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49923 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49926 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49940 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49945 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49970 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-49988 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50009 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50017 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50028 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50111 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50166 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50285 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50289 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52559 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-52560 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53051 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53056 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53079 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53085 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53089 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53090 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53091 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53094 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53114 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53134 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53187 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53195 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53219 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53221 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53224 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53687 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-54683 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56544 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56565 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56566 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56583 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56588 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56591 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56592 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56611 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56641 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56657 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56692 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56712 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56742 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57804 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57809 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57872 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57888 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57975 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57976 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57999 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58006 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58012 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58053 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58089 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58094 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58095 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58096 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58097 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-58098 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58100 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58237 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-58241 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21634 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21635 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21649 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21656 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21658 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21673 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21693 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21696 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21723 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21729 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21768 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21801 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21831 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21836 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21870 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21872 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21885 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21888 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21894 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21907 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21949 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21955 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21961 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21972 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21976 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22028 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22043 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22048 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22053 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22057 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22070 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22103 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22105 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22109 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22113 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22125 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-22127 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23129 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23130 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-23131 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-23132 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37747 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37800 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37802 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37806 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37807 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37833 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37834 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37842 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37853 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37856 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37860 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37864 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37880 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37893 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-37956 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-37977 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38006 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38014 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38029 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38038 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38039 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38041 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38042 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38045 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38059 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38064 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38080 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38096 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38127 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38132 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38140 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38195 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38203 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38207 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38237 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38244 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38246 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38261 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38264 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38272 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38283 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-38311 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38333 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38359 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38426 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38429 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38438 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38449 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38507 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38531 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38544 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38590 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38597 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38615 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38692 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38705 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38709 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38710 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38716 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39677 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39705 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39707 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39720 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39732 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39746 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39747 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39762 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39767 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39779 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39789 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39829 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39833 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39850 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39851 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39886 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39910 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39925 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39932 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39933 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39940 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39947 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39989 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40075 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40102 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40160 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40325 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40339 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68188 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68209 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68236 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68304 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-68379 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68823 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71109 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71129 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71138 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71160 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71184 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71188 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71202 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71227 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71272 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71273 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71285 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71289 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-71313 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22996 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23000 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23066 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23088 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23137 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23138 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23213 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23214 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23247 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23255 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23265 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23272 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23276 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23278 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23310 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23330 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23346 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23371 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23374 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23389 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23399 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23419 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23442 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23444 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23465 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23468 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23472 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31407 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31410 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31420 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31451 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31458 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31462 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31487 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31531 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31537 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31557 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31560 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31577 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31579 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31585 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31590 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31592 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31594 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31595 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31596 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31599 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31603 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31605 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31606 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31610 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31615 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31616 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31617 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31618 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31619 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31623 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31624 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31625 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31630 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31637 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31642 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31648 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31655 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31673 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31675 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31676 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-31677 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31681 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31684 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31692 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31698 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31699 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31701 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31704 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31722 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31723 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31724 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31725 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31767 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31771 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31777 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43009 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43010 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43016 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43022 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43036 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43042 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43048 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43058 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43064 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43071 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43072 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43073 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43079 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43080 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43083 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43085 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43088 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43089 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43091 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43093 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43094 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43098 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43099 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-43101 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43103 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43104 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43105 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43107 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43111 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43112 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43113 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43114 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-43115 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43118 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43119 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43129 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43137 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43153 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43161 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43167 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43170 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43172 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43173 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43204 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43213 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43215 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43216 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43219 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43234 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43244 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43271 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43288 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43299 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43308 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43309 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43310 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43317 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43318 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43338 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43344 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43350 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43352 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43353 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43362 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43409 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43413 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43416 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43421 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43443 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43456 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43492 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43502 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45834 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45835 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45836 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45838 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45841 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45842 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45843 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45844 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45846 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45855 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45943 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45944 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45961 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45963 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45981 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45985 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45986 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45987 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45988 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-45993 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45997 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45999 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46000 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46002 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46003 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46005 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46009 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46012 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46014 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46018 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46019 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46021 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46023 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46026 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46027 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46032 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46037 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46038 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46040 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46044 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46046 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46049 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46050 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46051 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46059 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46064 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46070 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46078 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46079 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46082 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46086 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46102 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46107 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46111 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46127 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46130 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46137 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-46146 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46147 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46148 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46151 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46153 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46156 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46157 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46158 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46160 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46161 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46165 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46167 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46168 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46169 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46170 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46172 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46179 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46184 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46186 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46190 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46193 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46196 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46200 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46214 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46220 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46225 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46226 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46229 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46231 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46233 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46235 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46236 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46245 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46252 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46254 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46273 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46280 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46291 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46304 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-46307 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46312 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46320 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46321 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46322 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2008-2544 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2011-4915 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2011-4916 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2011-4917 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9892 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2014-9900 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2016-10723 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-8660 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-13693 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-13694 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2018-12928 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12378 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12379 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12380 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12381 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-12382 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2019-12455 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-4543 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2023-31081 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31085 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-4134 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52653 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-53823 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53857 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54030 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-54088 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-35843 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-39990 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40057 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40196 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68219 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68334 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68378 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68794 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68822 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71315 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31486 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43253 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-43419 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43496 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45877 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45897 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45901 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45917 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46068 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46071 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46083 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46088 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46092 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46101 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46103 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46136 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46178 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46292 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46299 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46302 | MEDIUM4.67 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41079 | MEDIUM4.59 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-20643 | MEDIUM4.59 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-20665 | MEDIUM4.59 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-20643 | MEDIUM4.59 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-20665 | MEDIUM4.59 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1687 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2008-1688 | MEDIUM4.5 | m4 1.4.19-3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.9% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-55160 | MEDIUM4.5 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common-data 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-10+deb12u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | MEDIUM4.5 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz-icu0 6.0.0+dfsg-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22693 | MEDIUM4.5 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma-dev 5.4.1-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-55160 | MEDIUM4.5 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34380 | MEDIUM4.5 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | MEDIUM4.5 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-56226 | MEDIUM4.5 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32907 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32909 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1467 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1536 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1760 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2443 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2708 | MEDIUM4.5 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-32907 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-32909 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1467 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1536 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1760 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2443 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-2708 | MEDIUM4.5 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl-dev 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-36881 | MEDIUM4.5 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71225 | MEDIUM4.5 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-44173 | MEDIUM4.5 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34990 | MEDIUM4.42 | libcups2 2.4.2-3+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-40338 | MEDIUM4.42 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71193 | MEDIUM4.33 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-23035 | MEDIUM4.33 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmf-dev 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2007-3476 | MEDIUM4.3 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | krb5-multidev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-dev 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-33165 | MEDIUM4.25 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57360 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1176 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1181 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1182 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssrpc4 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5clnt-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkadm5srv-mit12 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkdb5-10 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-dev 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34589 | MEDIUM4.25 | libopenexr-dev 3.1.5-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-48959 | MEDIUM4.25 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng-dev 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | MEDIUM4.25 | libpng16-16 1.6.39-2+deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2005-3660 | MEDIUM4.17 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-60018 | MEDIUM4.08 | glib-networking 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60018 | MEDIUM4.08 | glib-networking-common 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60018 | MEDIUM4.08 | glib-networking-services 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54411 | MEDIUM4.08 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0716 | MEDIUM4.08 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6324 | MEDIUM4.08 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0716 | MEDIUM4.08 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6324 | MEDIUM4.08 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libfdisk1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-10041 | MEDIUM4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-20794 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-52771 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-53447 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-24864 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26869 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-27408 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36024 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-36949 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-39508 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42107 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46787 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-46870 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-50135 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53176 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-53178 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-56729 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57857 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-57974 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21651 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21732 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-21825 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-21892 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-22115 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38234 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38524 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-38717 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39726 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39754 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39927 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-39961 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-40139 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68296 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68745 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-71074 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23004 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23118 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23207 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23302 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23348 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23394 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-31697 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43053 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45949 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46017 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-46159 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-46187 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2019-16230 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16234 | MEDIUM4 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | uuid-dev 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6-dev 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-11082 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11082 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11083 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5244 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-5245 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-7545 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-7546 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6846 | LOW3.98 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW3.98 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-15213 | LOW3.91 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-4010 | LOW3.91 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2012-4542 | LOW3.91 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-20712 | LOW3.9 | binutils 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-common 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20712 | LOW3.9 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2008-3234 | LOW3.9 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-10524 | LOW3.9 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmf-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmf-dev 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2009-3546 | LOW3.85 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | 10.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-0840 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1179 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-66864 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66866 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69649 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69650 | LOW3.82 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2020-14304 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-54263 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42123 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40206 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68768 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-17977 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-26661 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26662 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26672 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26757 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26758 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26768 | LOW3.74 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2021-31879 | LOW3.66 | wget 1.21.3-1+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-10028 | LOW3.65 | glib-networking 2.74.0-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10028 | LOW3.65 | glib-networking-common 2.74.0-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-10028 | LOW3.65 | glib-networking-services 2.74.0-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | LOW3.65 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-25068 | LOW3.65 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-28861 | LOW3.65 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-20691 | LOW3.65 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28871 | LOW3.65 | libjavascriptcoregtk-4.0-18 2.50.6-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7-dev 2.5.0-2+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4035 | LOW3.65 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4476 | LOW3.65 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4035 | LOW3.65 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-4476 | LOW3.65 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28861 | LOW3.65 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-20691 | LOW3.65 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-28871 | LOW3.65 | libwebkit2gtk-4.0-37 2.50.6-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-5321 | LOW3.65 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3441 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3441 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3442 | LOW3.62 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-49219 | LOW3.57 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-31852 | LOW3.57 | libllvm15 1:15.0.6-4+b1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49219 | LOW3.57 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-41848 | LOW3.57 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | LOW3.54 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-1153 | LOW3.54 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2020-14145 | LOW3.54 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2016-1585 | LOW3.53 | libapparmor1 3.0.8-3 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-34152 | LOW3.53 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 8.0% Low-Moderate Risk | Post-Exploit |
| CVE-2010-4651 | LOW3.48 | patch 2.7.6-7 No fix yet | 4.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16089 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-42156 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-42158 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-16229 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16231 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-16232 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-16233 | LOW3.48 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | libdw1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-53589 | LOW3.37 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-53589 | LOW3.37 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-common 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2021-32256 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2023-1972 | LOW3.31 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7774 | LOW3.31 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-common 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2017-13716 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20673 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2018-9996 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2016-20012 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 5.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-15919 | LOW3.18 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-60019 | LOW3.15 | glib-networking 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60019 | LOW3.15 | glib-networking-common 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-60019 | LOW3.15 | glib-networking-services 2.74.0-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW3.15 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-7883 | LOW3.15 | libllvm15 1:15.0.6-4+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53462 | LOW3.15 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4945 | LOW3.15 | libsoup2.4-1 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-4945 | LOW3.15 | libsoup2.4-common 2.74.3-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2-dev 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4647 | LOW3.11 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4647 | LOW3.11 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2020-15778 | LOW3.07 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 13.0% High Exploitation Risk | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2007-2243 | LOW3 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2020-35501 | LOW2.89 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2019-6110 | LOW2.81 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 20.9% High Exploitation Risk | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11081 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11412 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11413 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11414 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11494 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11495 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11839 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11840 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-3198 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69651 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8224 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6844 | LOW2.8 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | cpp-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | g++-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.8 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45261 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo-script-interpreter2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2-dev 1.16.0-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66862 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66863 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66865 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69647 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69648 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69652 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8225 | LOW2.8 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncurses6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw5-dev 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libpam-systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-4016 | LOW2.8 | libproc2-0 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd-shared 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2-dev 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-2877 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-54227 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54233 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-54322 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50057 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-50211 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40268 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-40303 | LOW2.8 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW2.8 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | systemd-sysv 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | LOW2.78 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.20-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW2.7 | xz-utils 5.4.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libbinutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf-nobfd0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libctf0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1149 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1150 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1151 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-1180 | LOW2.63 | libgprofng0 2.40-2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1-dev 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2007-2768 | LOW2.58 | openssh-client 1:9.2p1-2+deb12u10 No fix yet | 8.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-57360 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-1176 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1181 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1182 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-6845 | LOW2.55 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | LOW2.55 | bzip2 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0992 | LOW2.46 | libxml2-dev 2.9.14+dfsg-1.3~deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68972 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4-openssl-dev 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-69644 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libbinutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf-nobfd0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libctf0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69644 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69645 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69646 | LOW2.38 | libgprofng0 2.40-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW2.29 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-24515 | LOW2.12 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2019-11191 | LOW2.12 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1152 | LOW1.89 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1152 | LOW1.89 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2007-3719 | LOW1.78 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66861 | LOW1.68 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-66861 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-66862 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66863 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-66865 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69647 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69648 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69652 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-8225 | LOW1.68 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | dirmngr 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gnupg-utils 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-agent 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-client 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpg-wks-server 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgconf 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgsm 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-4016 | LOW1.68 | procps 2:4.0.2-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-4217 | LOW1.68 | unzip 6.0-28 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-42155 | LOW1.61 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1148 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-common 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1148 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1149 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-1150 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1151 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-1180 | LOW1.58 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-common 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69644 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-69645 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69646 | LOW1.43 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-31437 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.39.5-0+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-30258 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gnupg-l10n 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | systemd 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b13 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-39043 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-39044 | NONE0 | gstreamer1.0-plugins-good 1.22.0-5+deb12u3 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick-6-common 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | imagemagick-6.q16 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-42046 | NONE0 | libcaca0 0.99.beta20-3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-51792 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38949 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-38950 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61147 | NONE0 | libde265-0 1.0.11-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libegl-mesa0 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libegl-mesa0 22.3.6-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libegl-mesa0 22.3.6-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libegl-mesa0 22.3.6-1+deb12u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libegl1 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-56131 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-56132 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libfdisk1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 22.3.6-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 22.3.6-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 22.3.6-1+deb12u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl-dev 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl1 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | libglapi-mesa 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglapi-mesa 22.3.6-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglapi-mesa 22.3.6-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglapi-mesa 22.3.6-1+deb12u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgles2 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx-dev 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 22.3.6-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 22.3.6-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 22.3.6-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 22.3.6-1+deb12u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx0 1.6.0-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 |
| CVE-2026-41069 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-25269 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-47178 | NONE0 | libheif1 1.15.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.14-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-dev 2.14-2+deb12u1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-6-arch-config 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-6.q16-6-extra 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickcore-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-6-headers 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-6.q16-6 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-6.q16-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| TEMP-1140176-50C86A | NONE0 | libmagickwand-dev 8:6.9.11.60+dfsg-1.6+deb12u10 No fix yet | — | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb-dev-compat 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-49261 | NONE0 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | libmariadb3 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44663 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | — | Not Applicable |
| CVE-2026-45696 | NONE0 | libopenexr-3-1-30 3.1.5-5 No fix yet | — | Not Applicable |
| CVE-2024-31047 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-44663 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | — | Not Applicable |
| CVE-2026-45696 | NONE0 | libopenexr-dev 3.1.5-5 No fix yet | — | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl-dev 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u7 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u7 No fix yet | — | Not Applicable |
| CVE-2023-45927 | NONE0 | libslang2 2.3.3-3 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-45929 | NONE0 | libslang2 2.3.3-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-dev 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-15661 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2026-55199 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2026-55200 | NONE0 | libssh2-1 1.10.0-3+b1 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl-dev 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff-dev 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiffxx6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-0.2-7 0.2.12-5.1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmf-dev 0.2.12-5.1 No fix yet | — | Not Applicable |
| TEMP-0601525-BEBB65 | NONE0 | libwmflite-0.2-7 0.2.12-5.1 No fix yet | — | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxbase3.2-1 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk-gl3.2-1 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk-webview3.2-1 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk-webview3.2-dev 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk3.2-1 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | libwxgtk3.2-dev 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31705 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-54125 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68201 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68315 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31587 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31597 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31598 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31602 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31611 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31612 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31622 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31626 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31627 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31629 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31711 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31712 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31716 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43075 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43076 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43117 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43495 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43497 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43499 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45839 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45850 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45930 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46006 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46031 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46058 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46062 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46072 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46075 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46077 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46080 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46091 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46098 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46108 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46109 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46110 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46112 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46122 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46124 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46128 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46129 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46143 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46164 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46177 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-46197 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46198 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46199 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46205 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46206 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46208 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46212 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46218 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46230 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46238 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46303 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46276 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46285 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46296 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46301 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-52909 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | — | Not Applicable |
| CVE-2026-52910 | NONE0 | linux-libc-dev 6.1.174-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-49261 | NONE0 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44168 | NONE0 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:10.11.14-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11 3.11.2-6+deb12u7 No fix yet | — | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-minimal 3.11.2-6+deb12u7 No fix yet | — | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | uuid-dev 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2024-58249 | NONE0 | wx-common 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58249 | NONE0 | wx3.2-headers 3.2.2+dfsg-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |