Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. It exposes a large attack surface with over 800 known vulnerabilities, the most severe of which (severity 7.8) allow local privilege escalation or remote denial-of-service conditions. Exploiting the util-linux bind-mount flaw (CVE-2026-78410) could let a local attacker gain elevated privileges, while the GLib XML parsing issue (CVE-2026-58016) may crash services processing untrusted D-Bus introspection data. Additionally, the image is not from a verified publisher, so its supply-chain provenance is uncertain. If deployed, strict network isolation, host hardening, and frequent patching are required to reduce likelihood of exploitation.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-78410 | HIGH7.8 | libmount1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-78410 | HIGH7.8 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-78410 | HIGH7.8 | libuuid1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85150 | HIGH7.5 | libgstreamer-plugins-base1.0-0 1.26.2-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2021-36691 | HIGH7.5 | libjxl0.11 0.11.2-0.1~deb13u2 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap2 2.6.10+dfsg-1 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | HIGH7.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | HIGH7.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.7.0-3+deb13u3 No fix yet | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-44950 | HIGH7.5 | libxfont2 1:2.0.6-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-59679 | HIGH7.5 | libxfont2 1:2.0.6-1+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5674 | HIGH7.48 | libpipewire-0.3-0t64 1.4.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5674 | HIGH7.48 | libspa-0.2-modules 1.4.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64830 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64831 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-64832 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64835 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66036 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66040 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75143 | HIGH7.48 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | HIGH7.48 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63387 | HIGH7.31 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63387 | HIGH7.31 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63387 | HIGH7.31 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63387 | HIGH7.31 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-63387 | HIGH7.31 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10729 | HIGH7.31 | libqt6svg6 6.8.2-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63388 | HIGH7.14 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63388 | HIGH7.14 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63388 | HIGH7.14 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63388 | HIGH7.14 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63388 | HIGH7.14 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2016-9580 | HIGH7.04 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2016-9581 | HIGH7.04 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.0% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-16376 | HIGH7.04 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-78409 | HIGH7 | libblkid1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libmount1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-78409 | HIGH7 | libuuid1 2.41.5-0+deb13u1 No fix yet | — | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-37555 | MEDIUM6.97 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75146 | MEDIUM6.88 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16554 | MEDIUM6.63 | libcjson1 1.7.18-3.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1365 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18297 | MEDIUM6.63 | libgstreamer-plugins-base1.0-0 1.26.2-1+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | MEDIUM6.63 | libnss3 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6labsplatform6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6qml6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6qmlcompiler6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6qmlmeta6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6qmlmodels6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6qmlnetwork6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6qmlworkerscript6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quick6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quickcontrols2-6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quickshapes6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quicktemplates2-6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quickvectorimage6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quickvectorimagegenerator6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | libqt6quickwidgets6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-66039 | MEDIUM6.63 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-66041 | MEDIUM6.63 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-70628 | MEDIUM6.63 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70632 | MEDIUM6.63 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-75142 | MEDIUM6.63 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-75144 | MEDIUM6.63 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-assets-downloader 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qml 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qmltime 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-animation 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-folderlistmodel 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-platform 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-qmlmodels 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-settings 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-sharedimage 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qt-labs-wavefrontmesh 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtcore 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtnetwork 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtqml 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtqml-models 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtqml-workerscript 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtqml-xmllistmodel 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-controls 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-dialogs 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-effects 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-layouts 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-localstorage 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-nativestyle 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-particles 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-shapes 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-templates 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-vectorimage 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14576 | MEDIUM6.63 | qml6-module-qtquick-window 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM6.54 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM6.54 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM6.54 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM6.54 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM6.54 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM6.54 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM6.54 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM6.54 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63382 | MEDIUM6.54 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63385 | MEDIUM6.54 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0856 | MEDIUM6.5 | libcaca0 0.99.beta20-5+deb13u1 No fix yet | 2.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | MEDIUM6.5 | libcairo2 1.18.4-1+b1 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1+b2 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | MEDIUM6.5 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.7.0-3+deb13u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58049 | MEDIUM6.46 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-29036 | MEDIUM6.38 | libcjson1 1.7.18-3.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-67215 | MEDIUM6.38 | libcjson1 1.7.18-3.1+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-67216 | MEDIUM6.38 | libcjson1 1.7.18-3.1+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34980 | MEDIUM6.38 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33164 | MEDIUM6.38 | libde265-0 1.0.15-1+deb13u1 fixed in 1.0.15-1+deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1t64 0.192-4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63383 | MEDIUM6.38 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63384 | MEDIUM6.38 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34872 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2018-1000520 | MEDIUM6.38 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-64834 | MEDIUM6.38 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-52490 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52491 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-52492 | MEDIUM6.21 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-64833 | MEDIUM6.03 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM6.03 | libtheoradec1 1.2.0~alpha1+dfsg-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5673 | MEDIUM6.03 | libtheoraenc1 1.2.0~alpha1+dfsg-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.11.0-7+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56109 | MEDIUM5.78 | libasound2t64 1.2.14-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap2 2.6.10+dfsg-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61915 | MEDIUM5.7 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-63381 | MEDIUM5.61 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30t64 3.8.9-3+deb13u4 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-client3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-68468 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-68471 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-24401 | MEDIUM5.52 | libavahi-common3 0.8-16 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34978 | MEDIUM5.52 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent-core-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent-extra-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent-openssl-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63379 | MEDIUM5.52 | libevent-pthreads-2.1-7t64 2.1.12-stable-10+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-25834 | MEDIUM5.52 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14324 | MEDIUM5.52 | libpipewire-0.3-0t64 1.4.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | MEDIUM5.52 | libpixman-1-0 0.44.0-3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6210 | MEDIUM5.52 | libqt6svg6 6.8.2-3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50613 | MEDIUM5.52 | libsndfile1 1.2.2-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14324 | MEDIUM5.52 | libspa-0.2-modules 1.4.2-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13858 | MEDIUM5.52 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6385 | MEDIUM5.52 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-66038 | MEDIUM5.52 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | MEDIUM5.5 | libcairo2 1.18.4-1+b1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27447 | MEDIUM5.35 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-39314 | MEDIUM5.27 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39316 | MEDIUM5.27 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.25.5-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76956 | MEDIUM5.02 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-66442 | MEDIUM5.02 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | util-linux 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-38350 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-client3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-59529 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68276 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34933 | MEDIUM4.67 | libavahi-common3 0.8-16 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-58436 | MEDIUM4.67 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | libminizip1t64 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-14330 | MEDIUM4.67 | libpipewire-0.3-0t64 1.4.2-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | MEDIUM4.67 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14330 | MEDIUM4.67 | libspa-0.2-modules 1.4.2-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-38350 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65703 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-65704 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65705 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-65706 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-66037 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-70629 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70630 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-70631 | MEDIUM4.67 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM4.67 | libudev1 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-23679 | MEDIUM4.67 | libusb-1.0-0 2:1.0.28-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47104 | MEDIUM4.67 | libusb-1.0-0 2:1.0.28-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | MEDIUM4.64 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | MEDIUM4.64 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18393 | MEDIUM4.59 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41079 | MEDIUM4.59 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.64.0-1.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-18393 | MEDIUM4.59 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-9079 | MEDIUM4.5 | curl 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2022-24975 | MEDIUM4.5 | git 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-9079 | MEDIUM4.5 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-30999 | MEDIUM4.5 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-client3 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2024-52615 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-52616 | MEDIUM4.5 | libavahi-common3 0.8-16 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-67217 | MEDIUM4.5 | libcjson1 1.7.18-3.1+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34979 | MEDIUM4.5 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16768 | MEDIUM4.5 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libgirepository-2.0-0 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0t64 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-bin 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | MEDIUM4.5 | libpng16-16t64 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6concurrent6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6core6t64 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6dbus6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6gui6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6network6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6opengl6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6openglwidgets6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6printsupport6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6sql6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6widgets6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | libqt6xml6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-30999 | MEDIUM4.5 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4360 | MEDIUM4.5 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-15037 | MEDIUM4.5 | qt6-qpa-plugins 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-52005 | MEDIUM4.49 | git 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-34990 | MEDIUM4.42 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-33165 | MEDIUM4.25 | libde265-0 1.0.15-1+deb13u1 fixed in 1.0.15-1+deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52584 | MEDIUM4.25 | libjxl0.11 0.11.2-0.1~deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.21.3-5+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12+deb13u3 No fix yet | — | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap2 2.6.10+dfsg-1 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.17 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76957 | MEDIUM4.17 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12216 | MEDIUM4.08 | libduktape207 2.7.0-2+b2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-81893 | MEDIUM4 | libgdk-pixbuf-2.0-0 2.42.12+dfsg-4+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap2 2.6.10+dfsg-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-11822 | LOW3.98 | sqlite3 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11824 | LOW3.98 | sqlite3 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.13-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9545 | LOW3.82 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW3.82 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | curl 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9080 | LOW3.72 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-25068 | LOW3.65 | libasound2t64 1.2.14-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.3-2.1~deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-25260 | LOW3.4 | libelf1t64 0.192-4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-10728 | LOW3.4 | libqt6svg6 6.8.2-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11856 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58051 | LOW3.31 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66033 | LOW3.31 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13346 | LOW3.31 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u3 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2014-8166 | LOW3.17 | libcups2t64 2.4.10-3+deb13u2 No fix yet | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-7883 | LOW3.15 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34873 | LOW3.06 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34875 | LOW3 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6653 | LOW3 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-1000021 | LOW3 | git 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.91 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libblkid1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libmount1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libuuid1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libblkid1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libblkid1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libmount1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libsmartcols1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libuuid1 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | mount 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.41.5-0+deb13u1 No fix yet | — | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-50812 | LOW2.8 | sqlite3 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50813 | LOW2.8 | sqlite3 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-50422 | LOW2.8 | libcairo-gobject2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.18.4-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3949 | LOW2.8 | libheif1 1.19.8-1+deb13u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13573 | LOW2.8 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13574 | LOW2.8 | libllvm19 1:19.1.7-3+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66035 | LOW2.7 | libssh2-1t64 1.11.1-1+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | LOW2.58 | sqlite3 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-8926 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW2.38 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.7.0-3+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1703 | LOW1.99 | python3-pip 25.1.1+dfsg-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.87 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.68 | sqlite3 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2005-1119 | LOW1.07 | sudo 1.9.16p2-3+deb13u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2019-1010022 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-8376 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8376 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58016 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13221 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42496 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34000 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-34002 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-52005 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-64830 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64830 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64831 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-64832 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64835 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66036 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66040 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75143 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74752 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63387 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-58014 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-23949 | NONE0 | python3-pkg-resources 78.1.1-0.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-23949 | NONE0 | python3-setuptools 78.1.1-0.1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-63388 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57432 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58010 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58012 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58013 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-75146 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78408 | NONE0 | libblkid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78408 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78408 | NONE0 | libmount-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78408 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78408 | NONE0 | uuid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-66039 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | libblkid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78410 | NONE0 | libblkid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-76642 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78410 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-76642 | NONE0 | libmount-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78410 | NONE0 | libmount-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-11695 | NONE0 | libnss3-dev 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-11696 | NONE0 | libnss3-dev 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-11697 | NONE0 | libnss3-dev 2:3.110-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11698 | NONE0 | libnss3-dev 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-11695 | NONE0 | libnss3-tools 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-11696 | NONE0 | libnss3-tools 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2017-11697 | NONE0 | libnss3-tools 2:3.110-1+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2017-11698 | NONE0 | libnss3-tools 2:3.110-1+deb13u4 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | libqt6quicktest6 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66039 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-66041 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-70628 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70632 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75142 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75144 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2013-7445 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 2.7% Low-Moderate Risk | Not Applicable |
| CVE-2019-19449 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2019-19814 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 3.3% Low-Moderate Risk | Not Applicable |
| CVE-2021-3847 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-21803 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-38137 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38187 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38206 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38421 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39859 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39862 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39958 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68735 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-23208 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31493 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46279 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53089 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53109 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53118 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72098 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-80536 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-12456 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-19378 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2020-11725 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2021-26934 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-25265 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-3238 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-26242 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-3640 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78410 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48962 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qml6-module-qtquick-tooling 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qml6-module-qttest 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qt6-declarative-dev 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qt6-declarative-dev-tools 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qt6-qmllint-plugins 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qt6-qmlls-plugins 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-14576 | NONE0 | qt6-qmltooling-plugins 6.8.2+dfsg-7 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76642 | NONE0 | uuid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78410 | NONE0 | uuid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-55999 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u3 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56000 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-49180 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-33999 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-34001 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34003 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-50256 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50257 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50258 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50259 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50260 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50261 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50264 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-55999 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56000 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63382 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-63385 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80590 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58049 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-24975 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2026-64834 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-63383 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63384 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-6829 | NONE0 | libgcrypt20-dev 1.11.0-7+deb13u1 No fix yet | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-58011 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-58011 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-58015 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64834 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2012-2663 | NONE0 | libxtables12 1.8.11-2 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-19070 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-0400 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2026-42497 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42497 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-9538 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68426 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-49176 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-49179 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-62229 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-62230 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-62231 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16118 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64833 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-58015 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22104 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38204 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38636 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23102 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23327 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31568 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46130 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53330 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40064 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43414 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64066 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64078 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2008-4609 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 32.1% High Exploitation Risk | Not Applicable |
| CVE-2026-78409 | NONE0 | libblkid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78409 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78409 | NONE0 | libmount-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2021-3864 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-68174 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43198 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46181 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52991 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53000 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53091 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53277 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63879 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64283 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68409 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68470 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72042 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72463 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74269 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74520 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74611 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74662 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80725 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40158 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40168 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46317 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46324 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46325 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-46330 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52953 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52956 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53009 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53224 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53246 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53250 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63941 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63979 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-64024 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64068 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64117 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64160 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64216 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64255 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64520 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68086 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68289 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68323 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68393 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68399 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68400 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68401 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68404 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68448 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68453 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72288 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72329 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72398 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-72499 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72500 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74289 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74405 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74496 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74506 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74513 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74533 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74534 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74537 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74695 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74697 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74715 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80521 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80668 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80693 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80698 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-1247 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-2961 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45884 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-45885 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-78409 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-78409 | NONE0 | uuid-dev 2.41.5-0+deb13u1 No fix yet | — | Not Applicable |
| CVE-2023-5574 | NONE0 | xserver-common 2:21.1.16-1.3+deb13u3 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-data 1.2.14-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-56109 | NONE0 | libasound2-dev 1.2.14-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-19499 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2025-40130 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2020-36694 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-6238 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-63381 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68468 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68471 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24401 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63379 | NONE0 | libevent-dev 2.1.12-stable-10+b1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-13858 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6385 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-66038 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-6240 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2025-68729 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-0564 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-15649 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40074 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-45932 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-44032 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-44033 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-3397 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40146 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15779 | NONE0 | libtdb1 2:1.4.13+samba4.22.10+dfsg-0+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40355 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68319 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-49175 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-49177 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-5435 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-80489 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-76956 | NONE0 | libexpat1-dev 2.8.3-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-2236 | NONE0 | libgcrypt20-dev 1.11.0-7+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2018-1121 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 4.2% Low-Moderate Risk | Not Applicable |
| CVE-2021-3714 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2026-15534 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-23039 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-59529 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68276 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-34933 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libblkid-dev 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-66382 | NONE0 | libexpat1-dev 2.8.3-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | libminizip-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | libmount-dev 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2021-4214 | NONE0 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-38350 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65703 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-65704 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65705 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-65706 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-66037 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-70629 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70630 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-70631 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-31082 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-37454 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-2193 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2024-25740 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52560 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-56709 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58074 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-58094 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58095 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21752 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-21949 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22108 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22109 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-22127 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-23132 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-23135 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37743 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37746 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-37880 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38029 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38036 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38041 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38042 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38064 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38132 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38140 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38199 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38203 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38205 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38207 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38237 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38261 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38284 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38311 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38359 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38597 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-38605 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-38621 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39677 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39762 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-39775 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39789 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39822 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39830 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39833 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39834 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39910 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39925 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-39933 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40102 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68209 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68236 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68304 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68353 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68368 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68730 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71117 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71141 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71188 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71202 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71227 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71285 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71302 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-71313 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-71315 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23007 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23017 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23137 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23143 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23152 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23217 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23259 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23265 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23371 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23377 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23385 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23472 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31435 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-31526 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31537 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31562 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31579 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31591 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31592 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31630 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31692 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31771 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-31777 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43009 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43022 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43029 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43034 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43042 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43048 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43083 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43101 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43115 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43118 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43127 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43172 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-43191 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43204 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43213 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-43234 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43272 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43294 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43298 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43299 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43301 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43308 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43309 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43310 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43311 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43325 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43326 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43337 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43344 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43346 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43352 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43353 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43416 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43443 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43463 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43464 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43465 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43485 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45934 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45940 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45961 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-45963 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46014 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46032 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46044 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46059 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46066 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46071 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46096 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46147 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46148 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46153 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46171 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46228 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46245 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46256 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46302 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46314 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52937 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52944 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52988 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52994 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53017 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53018 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53102 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53103 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53104 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53106 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53107 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53113 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53258 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-53281 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53285 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53292 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53297 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53313 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53321 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53377 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63832 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63853 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63858 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64006 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64036 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64038 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64058 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64060 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64067 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64070 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64076 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64077 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64079 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64146 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64154 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64159 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64190 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64210 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-64212 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64213 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68211 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68233 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68242 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68258 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68286 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68287 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-68291 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68295 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68312 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68382 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68383 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68421 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68435 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68441 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68447 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68471 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72073 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72162 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72334 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72337 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72341 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72355 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72365 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72367 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72375 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72380 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72383 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72388 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72397 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72402 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72404 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72413 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72423 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72438 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72440 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72454 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72488 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72493 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-72495 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74257 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74258 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74264 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74272 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74273 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74291 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74294 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74314 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74317 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74324 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74334 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74337 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74342 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74344 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74347 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74350 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74354 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74368 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74385 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74388 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74407 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74449 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74466 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74521 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74527 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74529 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74530 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74538 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74542 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74544 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74600 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74605 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74626 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-74638 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74687 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74711 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74713 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74723 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74729 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74735 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74747 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74753 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80557 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80562 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80572 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80579 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80580 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80583 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80614 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80623 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80628 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80631 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-80634 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80655 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80662 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80670 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-80671 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80692 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80721 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2008-2544 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2011-4915 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4916 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2011-4917 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9892 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2014-9900 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2016-10723 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2016-8660 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2017-13693 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2017-13694 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-12928 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12378 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12379 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12380 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12381 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-12382 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2019-12455 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-4543 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-31081 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-31085 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40086 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68193 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68359 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-53284 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63998 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63999 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64388 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64513 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68105 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68238 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68241 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68288 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68375 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68412 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68418 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68436 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72009 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72031 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72315 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72321 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72439 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72485 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72494 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-72496 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-72497 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74261 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74338 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74373 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74374 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-74375 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74558 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74559 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74560 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74571 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74653 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74728 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74733 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-74734 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74754 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80581 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80607 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80616 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80643 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-80653 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80705 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-24049 | NONE0 | python3-wheel 0.46.1-2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | uuid-dev 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-15853 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15859 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15861 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2018-15863 | NONE0 | x11-xkb-utils 7.7+9 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-49178 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50262 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50263 | NONE0 | xwayland 2:24.1.6-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-27171 | NONE0 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18393 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-52615 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2024-52616 | NONE0 | libavahi-common-data 0.8-16 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libblkid-dev 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2026-16768 | NONE0 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15588 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | liblastlog2-2 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | libmount-dev 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-3713 | NONE0 | libpng-dev 1.6.48-1+deb13u5 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-15037 | NONE0 | libqt6test6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-30999 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31437 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31438 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-31439 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12087 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15037 | NONE0 | qmake6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15037 | NONE0 | qmake6-bin 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15037 | NONE0 | qt6-base-dev 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15037 | NONE0 | qt6-base-dev-tools 6.8.2+dfsg-9+deb13u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | uuid-dev 2.41.5-0+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-40217 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40338 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | gir1.2-glib-2.0 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | gir1.2-glib-2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | girepository-tools 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2018-1000021 | NONE0 | git-man 1:2.47.3-0+deb13u1 No fix yet | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-42250 | NONE0 | libbz2-dev 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libgio-2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-data 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2012-0039 | NONE0 | libglib2.0-dev-bin 2.84.4-3~deb13u3 No fix yet | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-48959 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2004-0230 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 80.3% Actively Exploited | Not Applicable |
| CVE-2010-4563 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 3.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-48959 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-48959 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-48961 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76957 | NONE0 | libexpat1-dev 2.8.3-1~deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2005-3660 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-81893 | NONE0 | libgdk-pixbuf2.0-common 2.42.12+dfsg-4+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2019-20794 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-24864 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-37906 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-40139 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2025-68745 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-71074 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-23348 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-43053 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46017 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46272 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53108 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2017-0630 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2019-16230 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16234 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-15213 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2012-4542 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-68360 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2020-14304 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2018-17977 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-68337 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2-data 1.2.14-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25068 | NONE0 | libasound2-dev 1.2.14-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2021-45346 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-5321 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-19542 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | — | Not Applicable |
| CVE-2022-41848 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2019-16089 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16229 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16231 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2019-16232 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2019-16233 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-dev-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | libc6-dev 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2020-35501 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-70873 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libsystemd-dev 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2013-4392 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-40228 | NONE0 | libudev-dev 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2015-2877 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2025-68751 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2011-4116 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-40113 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2019-11191 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-3719 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-82208 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-13608 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-18924 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-19931 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80229 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80230 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80255 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82209 | NONE0 | curl 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-75141 | NONE0 | ffmpeg 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavcodec-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavcodec61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavdevice-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavdevice61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavfilter-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavfilter10 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavformat-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavformat61 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavutil-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libavutil59 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-82208 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-18924 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-19931 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80255 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl3t64-gnutls 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82208 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-13608 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-18924 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-19931 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80229 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80230 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-80255 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| CVE-2026-82209 | NONE0 | libcurl4t64 8.14.1-2+deb13u4 No fix yet | — | Not Applicable |
| TEMP-0000000-BB5891 | NONE0 | libde265-0 1.0.15-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-E66AA0 | NONE0 | libde265-0 1.0.15-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2023-45924 | NONE0 | libegl-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libegl-mesa0 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libegl-mesa0 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libegl-mesa0 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libegl-mesa0 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libegl1 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libegl1-mesa-dev 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libegl1-mesa-dev 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libegl1-mesa-dev 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libegl1-mesa-dev 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2026-66046 | NONE0 | libexpat1 2.8.3-1~deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-66046 | NONE0 | libexpat1-dev 2.8.3-1~deb13u1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm-dev 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm-dev 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm-dev 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm-dev 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgbm1 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libgl1 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgl1-mesa-dri 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libgles-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libgles1 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libgles2 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libgles2-mesa-dev 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libgles2-mesa-dev 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libgles2-mesa-dev 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libgles2-mesa-dev 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd-core-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglvnd0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45913 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | libglx-mesa0 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45924 | NONE0 | libglx0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1ED20C | NONE0 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1F4FF2 | NONE0 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-324AE3 | NONE0 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-905912 | NONE0 | libheif-plugin-dav1d 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1ED20C | NONE0 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1F4FF2 | NONE0 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-324AE3 | NONE0 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-905912 | NONE0 | libheif-plugin-libde265 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-84450 | NONE0 | libheif1 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-84451 | NONE0 | libheif1 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1ED20C | NONE0 | libheif1 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-1F4FF2 | NONE0 | libheif1 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-324AE3 | NONE0 | libheif1 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-905912 | NONE0 | libheif1 1.19.8-1+deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-82522 | NONE0 | libjxl0.11 0.11.2-0.1~deb13u2 No fix yet | — | Not Applicable |
| CVE-2025-29070 | NONE0 | liblcms2-2 2.16-2+deb13u2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-25835 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-25833 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34871 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-34877 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-25832 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-34874 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-34876 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-35336 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-49300 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50579 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50580 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50581 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50583 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50584 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50585 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50586 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50587 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50588 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50640 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-50713 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-54435 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-54441 | NONE0 | libmbedcrypto16 3.6.5-0.1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | libminizip-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | libminizip1t64 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | — | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl-dev 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45924 | NONE0 | libopengl0 1.7.0-1+b2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21C4F8 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8188AC | NONE0 | libpcre2-16-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-A5518C | NONE0 | libpcre2-16-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-B05303 | NONE0 | libpcre2-16-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21C4F8 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8188AC | NONE0 | libpcre2-32-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-A5518C | NONE0 | libpcre2-32-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-B05303 | NONE0 | libpcre2-32-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21C4F8 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8188AC | NONE0 | libpcre2-8-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-A5518C | NONE0 | libpcre2-8-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-B05303 | NONE0 | libpcre2-8-0 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-dev 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21C4F8 | NONE0 | libpcre2-dev 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8188AC | NONE0 | libpcre2-dev 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-A5518C | NONE0 | libpcre2-dev 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-B05303 | NONE0 | libpcre2-dev 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-86145 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-21C4F8 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-8188AC | NONE0 | libpcre2-posix3 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-A5518C | NONE0 | libpcre2-posix3 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| TEMP-0000000-B05303 | NONE0 | libpcre2-posix3 10.46-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | libperl5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libpostproc-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libpostproc58 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.13-stdlib 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6concurrent6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6core6t64 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6dbus6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6gui6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6labsplatform6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6network6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6opengl6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6openglwidgets6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6printsupport6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6qml6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6qmlcompiler6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6qmlmeta6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6qmlmodels6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6qmlnetwork6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6qmlworkerscript6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quick6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quickcontrols2-6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quickshapes6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quicktemplates2-6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quicktest6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quickvectorimage6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quickvectorimagegenerator6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | libqt6quickwidgets6 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6sql6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6test6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6widgets6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | libqt6xml6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45927 | NONE0 | libslang2 2.3.3-5+b2 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-45929 | NONE0 | libslang2 2.3.3-5+b2 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-39113 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39113 | NONE0 | libsqlite3-dev 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libswresample-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libswresample5 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libswscale-dev 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-75141 | NONE0 | libswscale8 7:7.1.5-0+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.7.0-3+deb13u3 No fix yet | — | Not Applicable |
| CVE-2025-25467 | NONE0 | libx264-164 2:0.164.3108+git31e19f9-2+b1 No fix yet | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-86137 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86138 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86139 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86140 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86141 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86142 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86143 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-86144 | NONE0 | libxml2 2.12.7+dfsg+really2.9.14-2.1+deb13u3 No fix yet | — | Not Applicable |
| CVE-2026-43185 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40025 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-31536 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-43263 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53010 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-74268 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-40065 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40136 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-40247 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68318 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68376 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68755 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-45956 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-46175 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-52983 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53024 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53025 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53178 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53368 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53401 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63805 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63811 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-63819 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-63825 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-63857 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-63859 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-64082 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-64389 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-64400 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-64581 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-68081 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-68303 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-72366 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-72501 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-74690 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-80737 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80738 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80747 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80755 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80759 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80761 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80762 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80763 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80764 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80765 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80766 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80767 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80768 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80770 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80771 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80772 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80774 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80779 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80780 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80781 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80782 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80783 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80784 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80785 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80786 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80788 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80789 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80790 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80791 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80792 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80793 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80794 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80795 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80796 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80797 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80798 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80799 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80800 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80801 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80802 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80803 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80805 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80806 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80807 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80808 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80809 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80812 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80814 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80815 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80819 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80820 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80822 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80823 | NONE0 | linux-libc-dev 6.12.105-1 fixed in 6.12.107-1 | — | Not Applicable |
| CVE-2026-80824 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80825 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80826 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80827 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80828 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80829 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80830 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80831 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80832 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80833 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80834 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80835 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80836 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80837 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80838 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80839 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80840 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80841 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80842 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80843 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80844 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80845 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80846 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80847 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80848 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80849 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80850 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80851 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80852 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80854 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80855 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80856 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80860 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80861 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80862 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80863 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80864 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80866 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80872 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80878 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80884 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80899 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| CVE-2026-80905 | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| TEMP-0000000-F7A20F | NONE0 | linux-libc-dev 6.12.105-1 No fix yet | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2023-45913 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | mesa-libgallium 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-45913 | NONE0 | mesa-va-drivers 25.0.7-2+deb13u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45919 | NONE0 | mesa-va-drivers 25.0.7-2+deb13u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2023-45922 | NONE0 | mesa-va-drivers 25.0.7-2+deb13u1 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-45931 | NONE0 | mesa-va-drivers 25.0.7-2+deb13u1 No fix yet | 1.0% Low-Moderate Risk | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-modules-5.40 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.13 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.13-minimal 3.13.5-2+deb13u4 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | qmake6 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | qmake6-bin 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-assets-downloader 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qml 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qmltime 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-animation 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-folderlistmodel 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-platform 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-qmlmodels 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-settings 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-sharedimage 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qt-labs-wavefrontmesh 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtcore 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtnetwork 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtqml 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtqml-models 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtqml-workerscript 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtqml-xmllistmodel 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-controls 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-dialogs 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-effects 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-layouts 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-localstorage 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-nativestyle 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-particles 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-shapes 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-templates 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-tooling 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-vectorimage 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qtquick-window 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qml6-module-qttest 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | qt6-base-dev 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | qt6-base-dev-tools 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qt6-declarative-dev 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qt6-declarative-dev-tools 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qt6-qmllint-plugins 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qt6-qmlls-plugins 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-12385 | NONE0 | qt6-qmltooling-plugins 6.8.2+dfsg-7 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2023-45935 | NONE0 | qt6-qpa-plugins 6.8.2+dfsg-9+deb13u2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39113 | NONE0 | sqlite3 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-82474 | NONE0 | sudo 1.9.16p2-3+deb13u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | — | Not Applicable |
| CVE-2026-85091 | NONE0 | zlib1g-dev 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | — | 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.