Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker could exploit CVE-2026-8461 in FFmpeg to execute arbitrary code via crafted media, or abuse CVE-2026-34873 in Mbed TLS to impersonate clients and gain unauthorized access. With 1,150 exposed vulnerabilities and an unverified community publisher, the image presents a large attack surface that is difficult to secure. Any production use would require exhaustive patching and network isolation.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-8461 | HIGH8.8 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8461 | HIGH8.8 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8461 | HIGH8.8 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8461 | HIGH8.8 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34873 | HIGH8.5 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34875 | HIGH8.33 | libmbedcrypto7 2.28.3-1 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.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6653 | HIGH8.33 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | HIGH8.33 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | 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-31486 | HIGH8.1 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | HIGH7.73 | libperl5.36 5.36.0-7+deb12u3 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.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-2026-13221 | HIGH7.73 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42496 | HIGH7.73 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54058 | HIGH7.73 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | 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-2026-29036 | HIGH7.5 | libcjson1 1.7.15-1+deb12u4 No fix yet | — | 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-2023-25193 | HIGH7.5 | libharfbuzz0b 6.0.0+dfsg-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2021-36691 | HIGH7.5 | libjxl0.7 0.7.0-10+deb12u1 No fix yet | 1.1% 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 | libkrb5-3 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-2024-23775 | HIGH7.5 | libmbedcrypto7 2.28.3-1 No fix yet | 1.1% 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-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 | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-69244 | HIGH7.5 | aiohttp 3.13.5 fixed in 3.14.3 | — | Directly Exposed |
| CVE-2026-67422 | HIGH7.5 | pymdown-extensions 10.21.3 fixed in 11.0.1 | — | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-23949 | HIGH7.31 | jaraco.context 5.3.0 fixed in 6.1.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH7.14 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-57432 | HIGH7.14 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-69243 | HIGH7 | aiohttp 3.13.5 fixed in 3.14.2 | — | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM6.97 | libsndfile1 1.2.0-1+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59197 | MEDIUM6.97 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59950 | MEDIUM6.88 | mcp 1.27.2 fixed in 1.28.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | 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-18220 | 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-18220 | 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-18220 | 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 | 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-18220 | 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-2025-52496 | MEDIUM6.63 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-45221 | MEDIUM6.63 | libmfx1 22.5.4-1 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-2026-66039 | MEDIUM6.63 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.4% 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-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48962 | MEDIUM6.63 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | 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+deb12u1 No fix yet | 2.7% 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 | 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-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 | libjbig0 2.1-6.1 No fix yet | 3.0% 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-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.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56208 | MEDIUM6.46 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70103 | MEDIUM6.46 | libjxl0.7 0.7.0-10+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.2% 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-2026-64834 | MEDIUM6.38 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.5% 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.6% 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-2026-67216 | MEDIUM6.38 | libcjson1 1.7.15-1+deb12u4 No fix yet | 0.3% 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.6% 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.6% 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-2025-1352 | MEDIUM6.38 | libelf1 0.188-2.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0 2.74.6-2+deb12u9 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.6% 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-2025-48965 | MEDIUM6.38 | libmbedcrypto7 2.28.3-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-34872 | MEDIUM6.38 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-1000520 | MEDIUM6.38 | libmbedcrypto7 2.28.3-1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-43615 | MEDIUM6.38 | libmbedcrypto7 2.28.3-1 No fix yet | 0.8% 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-2026-64834 | MEDIUM6.38 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59849 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM6.38 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM6.38 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-47265 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54273 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54274 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54277 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54278 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50269 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54275 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54279 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-54280 | MEDIUM6.38 | aiohttp 3.13.5 fixed in 3.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-12243 | MEDIUM6.38 | nltk 3.9.4 fixed in 3.10.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54293 | MEDIUM6.38 | nltk 3.9.4 fixed in 3.10.0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54059 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54060 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55379 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-55380 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59199 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59200 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59204 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59205 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59198 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59203 | MEDIUM6.38 | pillow 12.2.0 fixed in 12.3.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59935 | MEDIUM6.38 | pypdf 6.7.5 fixed in 6.14.2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59936 | MEDIUM6.38 | pypdf 6.7.5 fixed in 6.14.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-33699 | MEDIUM6.38 | pypdf 6.7.5 fixed in 6.9.2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59937 | MEDIUM6.38 | pypdf 6.7.5 fixed in 6.14.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15370 | MEDIUM6.21 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% 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-2026-11940 | MEDIUM6.21 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34993 | MEDIUM6.21 | aiohttp 3.13.5 fixed in 3.14.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-72522 | MEDIUM6.2 | libexpat1 2.5.0-1+deb12u2 No fix yet | — | Directly Exposed |
| CVE-2026-72522 | MEDIUM6.2 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | — | Directly Exposed |
| CVE-2026-18938 | MEDIUM6.2 | libp11-kit0 0.24.1-2 No fix yet | — | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56209 | MEDIUM6.03 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56210 | MEDIUM6.03 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56211 | MEDIUM6.03 | libaom3 3.6.0-1+deb12u2 No fix yet | 0.4% 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.3% 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.3% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.1% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u8 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-2025-15366 | MEDIUM6.03 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1153 | MEDIUM5.9 | libbinutils 2.40-2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | — | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-dev-bin 2.36-9+deb12u14 No fix yet | — | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | — | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6-dev 2.36-9+deb12u14 No fix yet | — | 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 | libk5crypto3 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 | 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-2026-56132 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16554 | MEDIUM5.78 | libcjson1 1.7.15-1+deb12u4 No fix yet | 0.3% Theoretical Threat | 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-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-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libbinutils 2.40-2 No fix yet | 0.8% 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.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6-dev 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libctf-nobfd0 2.40-2 No fix yet | 0.8% 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.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libctf0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2021-32256 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2023-1972 | MEDIUM5.52 | libgprofng0 2.40-2 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-23337 | MEDIUM5.52 | libjq1 1.6-2.1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% 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-2026-59843 | MEDIUM5.52 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | MEDIUM5.52 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | MEDIUM5.52 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33123 | MEDIUM5.52 | pypdf 6.7.5 fixed in 6.9.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41312 | MEDIUM5.52 | pypdf 6.7.5 fixed in 6.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41313 | MEDIUM5.52 | pypdf 6.7.5 fixed in 6.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41314 | MEDIUM5.52 | pypdf 6.7.5 fixed in 6.10.2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | — | 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-2026-19548 | MEDIUM5.5 | libbinutils 2.40-2 No fix yet | — | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u14 No fix yet | — | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-dev-bin 2.36-9+deb12u14 No fix yet | — | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u14 No fix yet | — | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6-dev 2.36-9+deb12u14 No fix yet | — | 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 | libcairo2 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-2026-19548 | MEDIUM5.5 | libctf-nobfd0 2.40-2 No fix yet | — | 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-2026-19548 | MEDIUM5.5 | libctf0 2.40-2 No fix yet | — | 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-2026-19548 | MEDIUM5.5 | libgprofng0 2.40-2 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70629 | MEDIUM5.5 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70630 | MEDIUM5.5 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-70631 | MEDIUM5.5 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | — | Directly Exposed |
| CVE-2026-71852 | MEDIUM5.5 | pypdf 6.7.5 fixed in 6.15.0 | — | Directly Exposed |
| CVE-2026-71870 | MEDIUM5.5 | pypdf 6.7.5 fixed in 6.15.0 | — | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.4% 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.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-61632 | MEDIUM5.3 | pymdown-extensions 10.21.3 fixed in 11.0.0 | — | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 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-4647 | MEDIUM5.18 | libbinutils 2.40-2 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-2026-4647 | MEDIUM5.18 | libgprofng0 2.40-2 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 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-stdlib 3.11.2-6+deb12u8 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 | libtiff6 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-2026-6019 | MEDIUM5.18 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54276 | MEDIUM5.18 | aiohttp 3.13.5 fixed in 3.14.1 | 0.2% 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.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | 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.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | 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-2026-27601 | MEDIUM5.02 | libjs-underscore 1.13.4~dfsg+~1.11.4-3 No fix yet | 0.9% 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 | libkrb5-3 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-2025-66442 | MEDIUM5.02 | libmbedcrypto7 2.28.3-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.4% Theoretical Threat | 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-2025-1178 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libbinutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf-nobfd0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libctf0 2.40-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1178 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15003 | MEDIUM4.76 | libgprofng0 2.40-2 No fix yet | 0.1% 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-10256 | MEDIUM4.67 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% 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.3% 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 | 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.3% 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.3% 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-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.2% 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.2% 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.2% 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.2% 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-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 | libgfortran5 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.3% 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-2025-9403 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40612 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u2 No fix yet | 0.2% 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-2024-23170 | MEDIUM4.67 | libmbedcrypto7 2.28.3-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-47169 | MEDIUM4.67 | libmfx1 22.5.4-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-48368 | MEDIUM4.67 | libmfx1 22.5.4-1 No fix yet | 0.2% 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-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% 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-2025-10256 | MEDIUM4.67 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-14330 | MEDIUM4.67 | libpulse0 16.1+dfsg1-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.1% 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-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-gcrypt-4 0.10.6-0+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-2025-10256 | MEDIUM4.67 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10256 | MEDIUM4.67 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% 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-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-2026-23679 | MEDIUM4.67 | libusb-1.0-0 2:1.0.26-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47104 | MEDIUM4.67 | libusb-1.0-0 2:1.0.26-1 No fix yet | 0.1% 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-2026-0864 | MEDIUM4.67 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% 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-55443 | MEDIUM4.67 | langchain 1.2.10 fixed in 1.3.9 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-31826 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.8.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48155 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.12.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-48735 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.12.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49461 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.12.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54530 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.13.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54531 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.13.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54651 | MEDIUM4.67 | pypdf 6.7.5 fixed in 6.13.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.52.0-1+deb12u3 No fix yet | 0.2% 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-2018-6951 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-6952 | MEDIUM4.5 | patch 2.7.6-7 No fix yet | 8.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-30999 | MEDIUM4.5 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libbinutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% 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.7% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libctf0 2.40-2 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf2.0-common 2.42.10+dfsg-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1147 | MEDIUM4.5 | libgprofng0 2.40-2 No fix yet | 0.7% 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-2024-28960 | MEDIUM4.5 | libmbedcrypto7 2.28.3-1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% 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-12087 | MEDIUM4.5 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% 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-2026-30999 | MEDIUM4.5 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% 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-2026-59848 | MEDIUM4.5 | libssh-gcrypt-4 0.10.6-0+deb12u2 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.5% 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 | libtiff6 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-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% 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-2026-12087 | MEDIUM4.5 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34452 | MEDIUM4.5 | anthropic 0.86.0 fixed in 0.87.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-25087 | MEDIUM4.5 | pyarrow 20.0.0 fixed in 23.0.1 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-40260 | MEDIUM4.5 | pypdf 6.7.5 fixed in 6.10.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-41168 | MEDIUM4.5 | pypdf 6.7.5 fixed in 6.10.1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59938 | MEDIUM4.5 | pypdf 6.7.5 fixed in 6.14.0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | MEDIUM4.49 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-64835 | MEDIUM4.49 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66036 | MEDIUM4.49 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66040 | MEDIUM4.49 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.39.5-0+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2024-45157 | MEDIUM4.33 | libmbedcrypto7 2.28.3-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-2026-57432 | MEDIUM4.28 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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.7% 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.6% 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-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.4% 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.4% 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.4% 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.4% 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.7% 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.6% 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.7% 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.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6845 | MEDIUM4.25 | libctf0 2.40-2 No fix yet | 0.1% 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.7% 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.6% 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-52584 | MEDIUM4.25 | libjxl0.7 0.7.0-10+deb12u1 No fix yet | 0.1% 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 | libkrb5-3 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-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 | libpng16-16 1.6.39-2+deb12u5 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-2026-48959 | MEDIUM4.25 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | MEDIUM4.25 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45829 | MEDIUM4.14 | chromadb 1.5.9 No fix yet | 12.4% High Exploitation Risk | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-27810 | MEDIUM4.08 | libmbedcrypto7 2.28.3-1 No fix yet | 0.3% 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 | libelf1 0.188-2.1 No fix yet | 0.3% 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 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% 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-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-18220 | 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-18220 | 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-18220 | 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-66039 | LOW3.98 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.4% 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-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-2025-15661 | LOW3.9 | libssh2-1 1.10.0-3+b1 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-58049 | LOW3.88 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | 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.6% 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.6% 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.6% 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-12064 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-64834 | LOW3.82 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW3.82 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% 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-56131 | LOW3.82 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56131 | LOW3.82 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-55798 | LOW3.82 | pillow 12.2.0 fixed in 12.3.0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-12474 | LOW3.74 | libjxl0.7 0.7.0-10+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34450 | LOW3.74 | anthropic 0.86.0 fixed in 0.87.0 | 0.1% 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-2026-25068 | LOW3.65 | libasound2 1.2.8-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb-dev 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44169 | LOW3.65 | libmariadb3 1:10.11.18-0+deb12u1 No fix yet | 0.2% 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-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.3% 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.3% 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.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-2024-31852 | LOW3.57 | libllvm15 1:15.0.6-4+b1 No fix yet | 1.0% 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-2023-6879 | LOW3.53 | libaom3 3.6.0-1+deb12u2 No fix yet | 1.2% 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-2025-47917 | LOW3.53 | libmbedcrypto7 2.28.3-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g-dev 1:1.2.13.dfsg-1 No fix yet | 3.2% 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-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-71176 | LOW3.47 | pytest 8.4.2 fixed in 9.0.3 | 0.1% Theoretical Threat | Post-Exploit |
| 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.8% 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.8% 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.8% 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-11856 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13858 | LOW3.31 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6385 | LOW3.31 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66038 | LOW3.31 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-23337 | LOW3.31 | jq 1.6-2.1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58051 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% 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-2026-59846 | LOW3.31 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| 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-2026-19548 | LOW3.3 | binutils 2.40-2 No fix yet | — | 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-2026-19548 | LOW3.3 | binutils-common 2.40-2 No fix yet | — | 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-2026-19548 | LOW3.3 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | — | Post-Exploit |
| CVE-2026-70629 | LOW3.3 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-70630 | LOW3.3 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-70631 | LOW3.3 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u15 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8461 | LOW3.17 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8461 | LOW3.17 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8461 | LOW3.17 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8461 | LOW3.17 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-8461 | LOW3.17 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-dev-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6-dev 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2016-9580 | LOW3.17 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2016-9581 | LOW3.17 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2018-16376 | LOW3.17 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| 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-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-2026-56391 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.1% 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-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-2026-59890 | LOW3.11 | setuptools 79.0.1 fixed in 83.0.0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% 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-2026-6357 | LOW2.96 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | 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-2025-1178 | LOW2.86 | binutils 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-common 2.40-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-1178 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-15003 | LOW2.86 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.1% Theoretical Threat | 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.3% 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.3% 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.3% 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-2025-10256 | LOW2.8 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-65703 | LOW2.8 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-65704 | LOW2.8 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-65705 | LOW2.8 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-65706 | LOW2.8 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-66037 | LOW2.8 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% 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-2025-9403 | LOW2.8 | jq 1.6-2.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.6-2.1+deb12u2 No fix yet | 0.2% 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-56288 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56289 | LOW2.8 | patch 2.7.6-7 No fix yet | 0.1% 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-2026-8643 | LOW2.8 | pip 24.0 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-24049 | LOW2.8 | wheel 0.45.1 fixed in 0.46.2 | 0.3% 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 | libcairo2 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-2011-4116 | LOW2.8 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u8 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-2026-0965 | LOW2.8 | libssh-gcrypt-4 0.10.6-0+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 | 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-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-2011-4116 | LOW2.8 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-48156 | LOW2.8 | pypdf 6.7.5 fixed in 6.12.0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49460 | LOW2.8 | pypdf 6.7.5 fixed in 6.12.2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW2.78 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-common 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-1147 | LOW2.7 | binutils-x86-64-linux-gnu 2.40-2 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% 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+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-30999 | LOW2.7 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% 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.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% 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-13595 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% 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-2025-8869 | LOW2.7 | pip 24.0 fixed in 25.3 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | 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.6% 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.7% 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.6% 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.7% 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.6% 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.7% 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.6% 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.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-gcrypt-4 0.10.6-0+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| 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.7% 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.6% 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.7% 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.6% 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.7% 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.6% 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-3219 | LOW2.55 | pip 24.0 fixed in 26.1 | 0.1% 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-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-51591 | LOW2.45 | pandoc 2.17.1.1-2~deb12u1 No fix yet | 0.6% 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-2026-10536 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u15 No fix yet | 0.4% 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-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 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+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl3-gnutls 7.88.1-10+deb12u15 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u15 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-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.1% 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 | 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-2026-1703 | LOW1.99 | pip 24.0 fixed in 26.0 | 0.4% Theoretical Threat | Post-Exploit |
| 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-2026-6879 | LOW1.87 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| 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-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 | 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-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.6% 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.7% 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.6% 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.7% 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.6% 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.7% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.48 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% 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-2026-68159 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68480 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-63797 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-39191 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52452 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52624 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-52751 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53218 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-26836 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26913 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-26914 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26944 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35887 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38570 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38630 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41045 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42118 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44941 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44942 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44951 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46729 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46811 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46813 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47691 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50029 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50217 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50226 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50282 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53068 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53168 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53179 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-53218 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56538 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56775 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57900 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21927 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21967 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-21969 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23133 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37750 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-37777 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37861 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37952 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37957 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38069 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38117 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38182 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38248 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38369 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38582 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38585 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38595 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38722 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38734 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-39797 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39810 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39952 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71068 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71073 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71152 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23171 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23226 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23361 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23447 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23448 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31527 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31663 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31729 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43049 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43250 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46068 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46219 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46241 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53115 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53117 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53120 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53129 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53143 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53156 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53262 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53272 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53361 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64270 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64271 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64272 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64273 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64274 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64530 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64531 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64564 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64600 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68143 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-46274 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.4% 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-2026-64396 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-68809 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40170 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68294 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2023-53781 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39981 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43248 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68121 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68278 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2024-26669 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41935 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53147 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57982 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21985 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22039 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38081 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38616 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39744 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39901 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45893 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45943 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45957 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46293 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53179 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-14040 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-25742 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-25743 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36013 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-53216 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68183 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68324 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43126 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-46135 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68155 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68188 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68373 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-52586 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42162 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37776 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40354 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23191 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31419 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43125 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46054 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53399 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63829 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63962 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64017 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64026 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64268 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64276 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64277 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64303 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64304 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64364 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64375 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64378 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64434 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64483 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64534 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64552 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64560 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64582 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68099 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68123 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68136 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68140 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68144 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68160 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68202 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68236 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68376 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68432 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2023-53762 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57984 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40328 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23050 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45859 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-45894 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45942 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46090 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46204 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46266 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53005 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53053 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53078 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53132 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53185 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53230 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53392 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63826 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63940 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64001 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64025 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64109 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64189 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64266 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64280 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64298 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64305 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64306 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64312 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64319 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64320 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64323 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64340 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64341 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64342 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64355 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64371 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64372 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64379 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64380 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64401 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64422 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64438 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64448 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64456 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64470 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64471 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64475 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64481 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64508 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64539 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64543 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64548 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64551 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64554 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64556 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64557 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64561 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64572 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64573 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64577 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68093 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68100 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68108 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68117 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68118 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68125 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68131 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68138 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68142 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68147 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68148 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68154 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68156 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68157 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68158 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68161 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68162 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68169 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68181 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68245 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68253 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68257 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68273 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68293 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68299 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68300 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68315 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68320 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68325 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68329 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68335 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68343 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68349 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68351 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68363 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68365 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68368 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68374 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68377 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68388 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68391 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68397 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68398 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68402 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68427 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68451 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68452 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72310 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-21264 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53095 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57795 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21714 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68284 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64296 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64322 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64324 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21759 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 7.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-53267 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-36968 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43239 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64535 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23383 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31502 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31516 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53090 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44034 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40307 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-40918 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40071 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68342 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68736 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31505 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68350 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2025-68320 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-53706 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54107 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54141 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23239 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23240 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-49569 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68198 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2023-0597 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-23005 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4133 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52590 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52591 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52625 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52629 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52648 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52671 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52676 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52761 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52770 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52797 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-52888 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52920 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53149 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53231 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53261 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53336 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53353 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53367 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53394 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53429 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53460 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53491 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53523 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53529 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53538 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53574 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-53627 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53846 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53999 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54013 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54280 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6039 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26670 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26677 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26691 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26740 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26756 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26799 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26841 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26866 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26876 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26902 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26947 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26948 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26953 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26962 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27010 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27011 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27041 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-27057 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27062 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27079 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35784 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35794 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35799 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35808 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35860 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35904 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35924 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35931 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35942 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35945 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35946 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35951 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35961 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36911 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36951 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38557 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38564 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38594 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38608 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38620 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38622 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-38625 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40965 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40969 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-40975 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40998 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-40999 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41008 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-41023 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41031 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-41082 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42128 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42139 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42239 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42241 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42243 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42279 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42317 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43819 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43824 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43850 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43872 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-43899 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43901 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-43913 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-44963 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-45015 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46678 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46681 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46698 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46727 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46728 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46730 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46754 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46760 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46765 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46775 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46776 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46806 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46808 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46834 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46860 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47141 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47658 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47661 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47662 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47664 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47703 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47752 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-47794 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49568 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49893 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49901 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49906 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49908 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49910 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49914 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49916 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49918 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49919 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49920 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49921 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49922 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49923 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49926 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49940 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49945 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49970 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-49988 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50009 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50017 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50028 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50111 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50166 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50285 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-50289 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52559 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53051 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53056 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53079 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53085 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53089 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53090 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53091 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53094 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53114 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53134 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53187 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53195 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53219 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53224 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53687 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-54683 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56544 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56565 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56566 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56583 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56588 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56591 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56592 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56611 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56641 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56692 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56712 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56742 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57804 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57809 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57872 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57888 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57975 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57976 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57999 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58006 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58012 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58053 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58089 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58096 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58097 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58098 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58100 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58237 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58241 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21634 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21635 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21649 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21656 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21658 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21673 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21693 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21696 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21723 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21729 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21768 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21801 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21831 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21836 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21870 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21872 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21885 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21888 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21894 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21907 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21955 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-21961 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-21972 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21976 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22028 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22037 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 65.7% Actively Exploited | Not Applicable |
| CVE-2025-22043 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-22048 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22053 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22057 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22070 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22103 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22113 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22125 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23129 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23130 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37747 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37800 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37802 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37806 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37807 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37833 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37834 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37842 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37853 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37856 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37860 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37893 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37956 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-37977 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38006 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38014 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38038 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38039 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38045 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38059 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38080 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38096 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38127 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38195 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38244 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38246 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38264 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38272 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38283 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38333 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38426 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38429 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38438 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38449 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38507 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38531 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38544 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38590 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38615 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38692 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38705 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38709 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38716 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39705 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39707 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39720 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39732 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39746 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39747 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39767 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39779 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39829 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39850 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39851 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39886 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39932 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39940 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39947 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39989 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40075 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40160 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40325 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40339 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68188 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68379 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71109 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71129 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71138 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71160 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71184 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71272 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71273 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71289 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-22996 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23000 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23088 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23138 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23213 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23214 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23247 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23276 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23330 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23346 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23374 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23419 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23465 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31410 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31420 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31458 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31462 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31487 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31531 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31557 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31560 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31606 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31610 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31648 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31655 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31675 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31677 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31722 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31723 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31724 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31725 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31767 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43010 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43016 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43036 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43073 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43088 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43091 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43107 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43119 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43129 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43137 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43153 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43161 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43167 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43170 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43173 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43215 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43216 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43244 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43271 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43288 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43317 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43318 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43338 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43362 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43409 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43413 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43419 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43456 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43491 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45855 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45858 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45877 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45892 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45897 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45899 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45901 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45917 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45944 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45981 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45985 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45988 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-45993 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46000 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-46012 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46111 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46156 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46157 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46158 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46170 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46200 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46225 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46226 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46229 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46254 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46282 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46312 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52936 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52961 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52990 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53015 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53027 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53070 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53076 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53083 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53122 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53220 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53226 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53229 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53232 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53237 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53265 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53317 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53332 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53345 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53353 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53358 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53376 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53393 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53400 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53402 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63847 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63848 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63854 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63856 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63963 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63983 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64112 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64163 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64187 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64192 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64206 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64241 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64248 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64250 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64275 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64279 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64294 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64297 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64299 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64313 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64315 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64316 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64329 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64330 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64333 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64336 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64338 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64343 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64344 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64346 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64347 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64351 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64360 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64362 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64363 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64365 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64373 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64374 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64381 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64403 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64406 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64408 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64409 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64411 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64412 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64413 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64423 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64424 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64436 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64450 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64452 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64454 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64455 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64458 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64463 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64472 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64478 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64487 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64496 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64507 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64510 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64540 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64541 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64542 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64545 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64546 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64547 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64549 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64553 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64567 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64569 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64576 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64579 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68085 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68091 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68096 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68098 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68104 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68106 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68111 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68112 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68113 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68114 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68127 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68129 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68130 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68135 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68137 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68141 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68146 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68152 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68153 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68180 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68182 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68183 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68184 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68186 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68187 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68189 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68190 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68194 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68195 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68196 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68197 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68204 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68205 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68206 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68207 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68209 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68210 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68212 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68214 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68215 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68222 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68229 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68231 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68243 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68244 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68246 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68247 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68248 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68255 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68259 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68269 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68277 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68279 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68297 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68309 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68310 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68322 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68324 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68326 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68338 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68344 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68352 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68353 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68354 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68355 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68357 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68360 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68362 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68364 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68366 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68367 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68369 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68371 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68395 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68396 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68410 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68411 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68413 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68414 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68417 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68425 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68428 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68431 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68433 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68444 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68445 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68446 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68449 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68454 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72025 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72305 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72428 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-4134 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-52653 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-53823 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53857 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54030 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54088 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-35843 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39990 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40057 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40196 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68219 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68334 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68378 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68794 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-68822 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31486 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43253 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63810 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63845 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63846 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63855 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63871 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63974 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64144 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64301 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64332 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64334 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64335 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64352 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64370 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64376 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64417 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64419 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64428 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64430 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64435 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64465 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64476 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64480 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64482 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64486 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64488 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64489 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64512 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64514 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64537 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64544 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68090 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68102 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68115 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68132 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68164 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68165 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68175 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68176 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68216 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68217 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68218 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68226 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68227 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68234 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68235 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68249 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68250 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68251 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68252 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68254 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68301 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68304 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68313 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68328 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68331 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68333 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68336 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68386 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68403 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68405 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68406 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68407 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68408 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68422 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68430 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68434 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68450 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72245 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72396 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2024-36881 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71225 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64538 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71193 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23035 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% 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-2004-0230 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-51591 | NONE0 | pandoc-data 2.17.1.1-2~deb12u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-52771 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-53447 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26869 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-27408 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36024 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-36949 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-39508 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42107 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46787 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-46870 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-50135 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53176 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-53178 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56729 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57857 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-57974 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21651 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21732 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-21825 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21892 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-22115 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38234 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38524 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-38717 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39726 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39754 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39927 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39961 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68296 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23004 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23118 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23207 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23394 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45949 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-4010 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-54263 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42123 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40206 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68768 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-26661 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26662 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26672 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26757 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26758 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-26768 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2-data 1.2.8-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-44169 | NONE0 | mariadb-common 1:10.11.18-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-42156 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-42158 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64317 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-54227 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-54233 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50057 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-50211 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40268 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40303 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-42155 | NONE0 | linux-libc-dev 6.1.177-1 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-53615 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| DLA-4726-1 | NONE0 | ca-certificates 20230311+deb12u1 fixed in 20250419~deb12u1 | — | Not Applicable |
| CVE-2026-64830 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | ffmpeg 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2 1.2.8-1+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.8-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-61627 | NONE0 | libass9 1:0.17.1-1 No fix yet | — | Not Applicable |
| CVE-2026-64830 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libavcodec59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libavdevice59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libavfilter8 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libavformat59 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libavutil57 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 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-67215 | NONE0 | libcjson1 1.7.15-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-67217 | NONE0 | libcjson1 1.7.15-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1-dev 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | 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+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglapi-mesa 22.3.6-1+deb12u2 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.6.0-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 22.3.6-1+deb12u2 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-2025-29070 | NONE0 | liblcms2-2 2.14-2+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-25835 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-27809 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-52497 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-54764 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-59438 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25833 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34871 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34877 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-28755 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25832 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-34874 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34876 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-35336 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-49300 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50579 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50580 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50581 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50583 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50584 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50585 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50586 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50587 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50588 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50640 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-50713 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-54435 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2026-54441 | NONE0 | libmbedcrypto7 2.28.3-1 No fix yet | — | Not Applicable |
| CVE-2023-22656 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-47282 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-48727 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21783 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-21808 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-28030 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-28051 | NONE0 | libmfx1 22.5.4-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 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-57433 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.4% 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-15534 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-19487 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libpostproc56 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-59986 | NONE0 | librabbitmq4 0.11.0-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-61547 | NONE0 | librabbitmq4 0.11.0-1+deb12u2 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-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | 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-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-2026-50812 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55868 | NONE0 | libsrt1.5-gnutls 1.5.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-55869 | NONE0 | libsrt1.5-gnutls 1.5.1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-14456 | NONE0 | libssl-dev 3.0.20-1~deb12u2 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-2026-14456 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.20-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libswresample4 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-70632 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | — | Not Applicable |
| CVE-2023-49528 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6601 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-31578 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2024-35369 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22921 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-36615 | NONE0 | libswscale6 7:5.1.9-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | libsystemd0 252.39-1~deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Not Applicable |
| CVE-2026-16742 | NONE0 | libudev1 252.39-1~deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-25467 | NONE0 | libx264-164 2:0.164.3095+gitbaee400-3 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-31432 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-31706 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43490 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64437 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40003 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40054 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40077 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40097 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40137 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40180 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40266 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40289 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40311 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40333 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40337 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68190 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68322 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71065 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71198 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23393 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31707 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43258 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63806 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63815 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63816 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63818 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63959 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64138 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64139 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64269 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-64318 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64331 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64337 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64345 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64348 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64350 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64359 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64361 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64390 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64391 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64392 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64393 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64394 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64395 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64397 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64398 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64399 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64420 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64425 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64429 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64432 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64440 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64441 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64442 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64443 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64444 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64445 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64446 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64449 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64461 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64462 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64468 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64469 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64484 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64494 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64495 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64497 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64500 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64503 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64504 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64505 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64532 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64533 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64536 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64550 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64562 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64563 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64565 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64571 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64578 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64580 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64583 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64584 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64585 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-64586 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64590 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-64593 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-64594 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-64599 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-64602 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-64604 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68082 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68083 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68084 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68088 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68097 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68124 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68151 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68185 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68192 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68199 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68203 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68213 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68223 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68280 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68302 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68327 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68340 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68359 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68361 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68370 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68456 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68457 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68459 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68460 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68461 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68466 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68467 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68469 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68474 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68475 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68476 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-68477 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68478 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-68479 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72004 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72005 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72007 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72010 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72012 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72013 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72014 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72015 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72017 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72019 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72020 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72021 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72022 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72023 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72024 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72028 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72029 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72030 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72033 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72035 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72036 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72037 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72038 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72039 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72040 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72041 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72043 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72045 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72047 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72048 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72049 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72051 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72052 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72053 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72054 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72055 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72056 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72057 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72058 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72059 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72061 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72062 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72063 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72065 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72066 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72067 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72068 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72069 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72070 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72072 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72074 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72075 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72076 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72077 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72078 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72079 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72081 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72082 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72083 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72084 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72085 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72086 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72087 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72088 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72096 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72097 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72099 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72102 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72105 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72106 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72107 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72108 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72109 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72110 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72113 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72114 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72115 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72116 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72117 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72118 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72119 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72120 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72121 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72122 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72123 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72124 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72125 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72126 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72129 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72130 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72133 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72135 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72136 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72138 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72140 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72142 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72144 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72146 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72147 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72148 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72149 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72150 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72152 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72153 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72155 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72156 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72157 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72159 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72160 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72161 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72163 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72164 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72165 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72166 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72167 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72168 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72170 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72171 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72172 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72177 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72179 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72181 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72182 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72191 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72192 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72193 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72194 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72195 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72196 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72197 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72198 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72199 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72200 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72201 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72202 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72203 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72204 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72205 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72206 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72207 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72208 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72210 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72211 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72213 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72214 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72215 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72216 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72218 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72219 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72223 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72224 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72225 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72226 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72228 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72229 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72230 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72231 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72232 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72233 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72234 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72235 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72236 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72237 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72238 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72240 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72241 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72242 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72243 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72247 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72250 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72251 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72252 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72253 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72254 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72255 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72256 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72257 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72260 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72261 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72262 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72264 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72265 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72267 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72268 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72269 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72270 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72271 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72272 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72274 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72275 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72276 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72282 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72284 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72289 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72290 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72296 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72297 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72298 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72299 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72301 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72302 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72306 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72307 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72308 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72312 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72314 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72316 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72318 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72319 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72320 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72322 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72323 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72324 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72325 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72326 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72335 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72336 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72338 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72339 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72342 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72343 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72347 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72348 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72349 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72350 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72351 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72369 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72371 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72373 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72374 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72376 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72378 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72379 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72382 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72384 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72389 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72390 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72391 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72392 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72399 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72400 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72405 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72406 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72409 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72414 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72416 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72418 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72419 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72420 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72421 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72422 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72424 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72425 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72433 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72434 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72435 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72436 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72437 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72441 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72444 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72447 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72448 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72449 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72450 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72459 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72460 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72464 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72466 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72467 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72469 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72470 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72472 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72473 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72476 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72478 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72479 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72480 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72481 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72483 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72484 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72486 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72487 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72489 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72491 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72492 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-72502 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74255 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74256 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74259 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74262 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74265 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74267 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74271 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74276 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74278 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74279 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74280 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74281 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74282 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74283 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74284 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74287 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74288 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74290 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74292 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74293 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74295 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74296 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74297 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74300 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74302 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74305 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74307 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74308 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74310 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74312 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74313 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74318 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74320 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74321 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74327 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74329 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74330 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74331 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74339 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74340 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74341 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74345 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74346 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74348 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74349 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74351 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74356 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74359 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74363 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74365 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74376 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74377 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74378 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74379 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74380 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74381 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74382 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74384 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74386 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74387 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74389 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74390 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74391 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74394 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74395 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74397 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74398 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74399 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74401 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74402 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74406 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74408 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74410 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74416 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74417 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74424 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74426 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74427 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74436 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74438 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-74441 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74443 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74444 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74445 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74446 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74448 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74450 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74453 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74454 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74455 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74456 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74457 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74458 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74459 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74460 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74461 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74463 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74464 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74465 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74467 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74468 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74469 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74470 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74471 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74472 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74473 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74474 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74475 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74476 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74478 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74479 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74480 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74481 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74482 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74484 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74485 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74487 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74488 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74490 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74492 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74493 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74494 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74495 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74497 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74498 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74499 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74505 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74507 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74508 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74509 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74510 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74512 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74514 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74515 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74516 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74518 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74519 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74522 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74523 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74525 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74536 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74540 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74543 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74546 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74547 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74548 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74549 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74550 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74551 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74552 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74553 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74555 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74556 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74557 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74563 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74564 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74565 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74566 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74567 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74569 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74575 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74577 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2026-74578 | NONE0 | linux-libc-dev 6.1.177-1 fixed in 6.1.180-1 | — | Not Applicable |
| CVE-2026-43249 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| CVE-2023-53851 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74579 | NONE0 | linux-libc-dev 6.1.177-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-14456 | NONE0 | openssl 3.0.20-1~deb12u2 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-57433 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-19487 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% 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-15534 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.4% 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-15534 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.36 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-dev 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-minimal 3.11.2-6+deb12u8 No fix yet | 0.1% Theoretical Threat | 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-53615 | NONE0 | util-linux 2.38.1-5+deb12u3 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-extra 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 |
| GHSA-4gmw-gg2m-w46p | NONE0 | GitPython 3.1.57 fixed in 3.1.58 | — | Not Applicable |
| GHSA-9rj7-rf2p-w77r | NONE0 | GitPython 3.1.57 fixed in 3.1.58 | — | Not Applicable |
| GHSA-hmq2-w58f-27jc | NONE0 | GitPython 3.1.57 fixed in 3.1.58 | — | Not Applicable |
| GHSA-jm78-9fvv-mhgr | NONE0 | GitPython 3.1.57 fixed in 3.1.58 | — | Not Applicable |
| GHSA-wvpp-8hx9-p66j | NONE0 | GitPython 3.1.57 fixed in 3.1.58 | — | Not Applicable |
| GHSA-hh9p-6wh2-4mfc | NONE0 | GitPython 3.1.57 fixed in 3.1.58 | — | Not Applicable |
| CVE-2026-59881 | NONE0 | aiohttp 3.13.5 fixed in 3.14.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-69247 | NONE0 | cryptography 48.0.0 fixed in 50.0.0 | — | Not Applicable |
| CVE-2026-69249 | NONE0 | cryptography 48.0.0 fixed in 49.0.0 | — | Not Applicable |
| GHSA-537c-gmf6-5ccf | NONE0 | cryptography 48.0.0 fixed in 48.0.1 | — | Not Applicable |
| CVE-2026-69248 | NONE0 | cryptography 48.0.0 fixed in 49.0.0 | — | Not Applicable |
| CVE-2026-71554 | NONE0 | h2 4.4.0 fixed in 4.4.1 | — | Not Applicable |
| CVE-2026-12061 | NONE0 | nltk 3.9.4 fixed in 3.10.0 | — | Not Applicable |
| CVE-2026-12072 | NONE0 | nltk 3.9.4 fixed in 3.10.0 | — | Not Applicable |
| CVE-2026-12074 | NONE0 | nltk 3.9.4 fixed in 3.10.0 | — | Not Applicable |
| CVE-2026-12075 | NONE0 | nltk 3.9.4 fixed in 3.10.0 | — | Not Applicable |
| GHSA-jm82-fx9c-mx94 | NONE0 | pypdf 6.7.5 fixed in 6.13.3 | — | Not Applicable |
| CVE-2025-3000 | NONE0 | torch 2.9.1+cpu fixed in 2.13.0 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-3001 | NONE0 | torch 2.9.1+cpu fixed in 2.10.0 | 0.2% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.