Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. The container runs tshark for live packet analysis and exposes 859 vulnerabilities, including 47 with severity >= 7, the most impactful being CVE-2026-76886 (severity 8.33) which can cause a remote denial of service via crafted C12.22 packets. CVE-2026-45447 in OpenSSL (severity 8.1) introduces a use-after-free that could lead to crashes or memory corruption when processing PKCS#7/S/MIME data. Using a capture filter to exclude C12.22 protocol fully mitigates CVE-2026-76886; otherwise, ensure the container only processes trusted network traffic.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-76886 | HIGH8.33 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-76886 | HIGH8.33 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-76886 | HIGH8.33 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-76886 | HIGH8.33 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-76886 | HIGH8.33 | tshark 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-76886 | HIGH8.33 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: HIGH |
| CVE-2026-45447 | HIGH8.1 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 3.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-58016 | HIGH7.73 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | HIGH7.73 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | HIGH7.73 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | HIGH7.73 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13878 | HIGH7.5 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.44-1~deb12u1 | 8.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-1519 | HIGH7.5 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.47-1~deb12u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-3039 | HIGH7.5 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-5946 | HIGH7.5 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc-bin 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc-bin 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | HIGH7.5 | libc6 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | HIGH7.5 | libc6 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | HIGH7.5 | libexpat1 2.5.0-1+deb12u2 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | HIGH7.5 | libgcrypt20 1.10.1-3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-33846 | HIGH7.5 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42009 | HIGH7.5 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libip4tc2 1.8.9-2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libip6tc2 1.8.9-2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | HIGH7.5 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2953 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2015-3276 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 5.3% Low-Moderate Risk | Directly Exposed |
| CVE-2017-17740 | HIGH7.5 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 7.0% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16226 | HIGH7.5 | liblmdb0 0.9.24-1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2019-16228 | HIGH7.5 | liblmdb0 0.9.24-1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13836 | HIGH7.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | HIGH7.5 | libssl3 3.0.17-1~deb12u3 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-52355 | HIGH7.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2017-16232 | HIGH7.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 5.4% Low-Moderate Risk | Directly Exposed |
| CVE-2012-2663 | HIGH7.5 | libxtables12 1.8.9-2 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2025-5372 | HIGH7.48 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13321 | HIGH7.31 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58014 | HIGH7.31 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Directly Exposed |
| CVE-2026-53613 | HIGH7 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Directly Exposed |
| CVE-2026-58010 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM6.97 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42013 | MEDIUM6.97 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5260 | MEDIUM6.97 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0966 | MEDIUM6.97 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0861 | MEDIUM6.88 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6100 | MEDIUM6.88 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-28387 | MEDIUM6.88 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc-bin 2.36-9+deb12u13 No fix yet | — | Directly Exposed |
| CVE-2026-19499 | MEDIUM6.8 | libc6 2.36-9+deb12u13 No fix yet | — | Directly Exposed |
| CVE-2025-14087 | MEDIUM6.66 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u8 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6653 | MEDIUM6.66 | libxml2 2.9.14+dfsg-1.3~deb12u4 No fix yet | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-1365 | MEDIUM6.63 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1372 | MEDIUM6.63 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-25210 | MEDIUM6.63 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM6.63 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM6.63 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4775 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u3 fixed in 4.5.0-6+deb12u4 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-8176 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8177 | MEDIUM6.63 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM6.63 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5403 | MEDIUM6.63 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5405 | MEDIUM6.63 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5656 | MEDIUM6.63 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5403 | MEDIUM6.63 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5405 | MEDIUM6.63 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5656 | MEDIUM6.63 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5403 | MEDIUM6.63 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5405 | MEDIUM6.63 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5656 | MEDIUM6.63 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5403 | MEDIUM6.63 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5405 | MEDIUM6.63 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5656 | MEDIUM6.63 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11979 | MEDIUM6.63 | libxml2 2.9.14+dfsg-1.3~deb12u4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5403 | MEDIUM6.63 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5405 | MEDIUM6.63 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5656 | MEDIUM6.63 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13601 | MEDIUM6.54 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | MEDIUM6.5 | libjbig0 2.1-6.1 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6277 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-10126 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2022-1210 | MEDIUM6.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11331 | MEDIUM6.38 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11605 | MEDIUM6.38 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11622 | MEDIUM6.38 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-11721 | MEDIUM6.38 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12617 | MEDIUM6.38 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13204 | MEDIUM6.38 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-1352 | MEDIUM6.38 | libelf1 0.188-2.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45186 | MEDIUM6.38 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41989 | MEDIUM6.38 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM6.38 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM6.38 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libgssapi-krb5-2 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-32316 | MEDIUM6.38 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40164 | MEDIUM6.38 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libk5crypto3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libk5crypto3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5-3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5-3 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40355 | MEDIUM6.38 | libkrb5support0 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40356 | MEDIUM6.38 | libkrb5support0 1.20.1-2+deb12u4 fixed in 1.20.1-2+deb12u5 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27135 | MEDIUM6.38 | libnghttp2-14 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69534 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-15308 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3644 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4224 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-7210 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-8194 | MEDIUM6.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-3731 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-59847 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-59849 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-59850 | MEDIUM6.38 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-54874 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM6.38 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-9781 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1492 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9817 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15163 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15169 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3201 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3203 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5653 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5654 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5657 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6519 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6520 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6868 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7375 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7376 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7378 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7379 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76888 | MEDIUM6.38 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-9781 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1492 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9817 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15163 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15169 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3201 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3203 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5653 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5654 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5657 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6519 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6520 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6868 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7375 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7376 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7378 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7379 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76888 | MEDIUM6.38 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-9781 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1492 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9817 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15163 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15169 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3201 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3203 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5653 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5654 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5657 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6519 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6520 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6868 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7375 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7376 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7378 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7379 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76888 | MEDIUM6.38 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-9781 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1492 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9817 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15163 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15169 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3201 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3203 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5653 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5654 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5657 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6519 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6520 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6868 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7375 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7376 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7378 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7379 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76888 | MEDIUM6.38 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-9781 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-1492 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9817 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15163 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15169 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3201 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3203 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5653 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5654 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5657 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6519 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6520 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6868 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7375 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7376 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7378 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7379 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76888 | MEDIUM6.38 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3833 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42011 | MEDIUM6.29 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM6.29 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29481 | MEDIUM6.21 | libbpf1 1:1.1.2-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | MEDIUM6.21 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15370 | MEDIUM6.21 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-12912 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-52490 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61144 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-52492 | MEDIUM6.21 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-54369 | MEDIUM6.03 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM6.03 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42012 | MEDIUM6.03 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15367 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-1299 | MEDIUM6.03 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.66-4+deb12u2 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | — | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | — | Directly Exposed |
| CVE-2024-2236 | MEDIUM5.9 | libgcrypt20 1.10.1-3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | MEDIUM5.9 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-13151 | MEDIUM5.9 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-56132 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56403 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56404 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56405 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56406 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56407 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56410 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-56411 | MEDIUM5.87 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-10723 | MEDIUM5.78 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22185 | MEDIUM5.78 | liblmdb0 0.9.24-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-42014 | MEDIUM5.61 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | MEDIUM5.61 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.59 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-10822 | MEDIUM5.52 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31147 | MEDIUM5.52 | libc-ares2 1.18.1-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14512 | MEDIUM5.52 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u8 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-39979 | MEDIUM5.52 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-23337 | MEDIUM5.52 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11972 | MEDIUM5.52 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-5351 | MEDIUM5.52 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59843 | MEDIUM5.52 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-59844 | MEDIUM5.52 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-5601 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5406 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5408 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6521 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6522 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6524 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6529 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6530 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6533 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6535 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6537 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6538 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6867 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6869 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76879 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76928 | MEDIUM5.52 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5601 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5406 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5408 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6521 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6522 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6524 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6529 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6530 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6533 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6535 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6537 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6538 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6867 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6869 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76879 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76928 | MEDIUM5.52 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5601 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5406 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5408 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6521 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6522 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6524 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6529 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6530 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6533 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6535 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6537 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6538 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6867 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6869 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76879 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76928 | MEDIUM5.52 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5601 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5406 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5408 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6521 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6522 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6524 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6529 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6530 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6533 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6535 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6537 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6538 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6867 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6869 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76879 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76928 | MEDIUM5.52 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-5601 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5406 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5408 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6521 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6522 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6524 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6529 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6530 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6533 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6535 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6537 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6538 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6867 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6869 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76879 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76928 | MEDIUM5.52 | tshark 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0964 | MEDIUM5.35 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.36-9+deb12u13 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-59375 | MEDIUM5.3 | libexpat1 2.5.0-1+deb12u2 No fix yet | 1.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-72522 | MEDIUM5.27 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | MEDIUM5.27 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-1757 | MEDIUM5.27 | libxml2 2.9.14+dfsg-1.3~deb12u4 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-39956 | MEDIUM5.18 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | MEDIUM5.18 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | MEDIUM5.18 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.02 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.02 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-50219 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56412 | MEDIUM5.02 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | MEDIUM5.02 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-9669 | MEDIUM5.02 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59845 | MEDIUM5.02 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-0990 | MEDIUM5.02 | libxml2 2.9.14+dfsg-1.3~deb12u4 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | MEDIUM5 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-25629 | MEDIUM4.67 | libc-ares2 1.18.1-3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM4.67 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1371 | MEDIUM4.67 | libelf1 0.188-2.1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-1377 | MEDIUM4.67 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32776 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32777 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-32778 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-33947 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41256 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41257 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-43894 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-43896 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-44777 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-47770 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54679 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9403 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40612 | MEDIUM4.67 | libjq1 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6075 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0864 | MEDIUM4.67 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | MEDIUM4.67 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0967 | MEDIUM4.67 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | MEDIUM4.67 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-3164 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6228 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-61143 | MEDIUM4.67 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-11596 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11626 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13499 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13945 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13946 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0960 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15164 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15166 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15167 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15170 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15171 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15172 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15174 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5299 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5401 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5404 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5407 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5409 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6523 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6527 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6532 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6534 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6870 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76880 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76917 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76918 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76923 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76924 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9759 | MEDIUM4.67 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-11596 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11626 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13499 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13945 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13946 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0960 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15164 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15166 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15167 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15170 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15171 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15172 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15174 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5299 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5401 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5404 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5407 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5409 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6523 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6527 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6532 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6534 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6870 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76880 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76917 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76918 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76923 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76924 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9759 | MEDIUM4.67 | libwireshark16 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-11596 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11626 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13499 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13945 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13946 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0960 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15164 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15166 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15167 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15170 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15171 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15172 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15174 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5299 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5401 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5404 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5407 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5409 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6523 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6527 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6532 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6534 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6870 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76880 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76917 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76918 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76923 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76924 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9759 | MEDIUM4.67 | libwiretap13 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-11596 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11626 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13499 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13945 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13946 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0960 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15164 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15166 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15167 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15170 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15171 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15172 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15174 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5299 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5401 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5404 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5407 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5409 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6523 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6527 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6532 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6534 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6870 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76880 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76917 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76918 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76923 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76924 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9759 | MEDIUM4.67 | libwsutil14 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-9714 | MEDIUM4.67 | libxml2 2.9.14+dfsg-1.3~deb12u4 fixed in 2.9.14+dfsg-1.3~deb12u5 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-11596 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-11626 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13499 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-13945 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13946 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-0960 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15164 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15166 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15167 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15170 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15171 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15172 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15174 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5299 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5401 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5404 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5407 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5409 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6523 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6527 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6532 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6534 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6870 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76880 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-76917 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76918 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76923 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76924 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-9759 | MEDIUM4.67 | tshark 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7598 | MEDIUM4.64 | libssh2-1 1.10.0-3+b1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1489 | MEDIUM4.59 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | MEDIUM4.59 | libnghttp2-14 1.52.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13878 | MEDIUM4.5 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.44-1~deb12u1 | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1519 | MEDIUM4.5 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.47-1~deb12u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3039 | MEDIUM4.5 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5946 | MEDIUM4.5 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13878 | MEDIUM4.5 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.44-1~deb12u1 | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1519 | MEDIUM4.5 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.47-1~deb12u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3039 | MEDIUM4.5 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5946 | MEDIUM4.5 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13878 | MEDIUM4.5 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.44-1~deb12u1 | 8.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1519 | MEDIUM4.5 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.47-1~deb12u1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3039 | MEDIUM4.5 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-5946 | MEDIUM4.5 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2012-2663 | MEDIUM4.5 | iptables 1.8.9-2 No fix yet | 2.8% Low-Moderate Risk | Post-Exploit |
| CVE-2026-63076 | MEDIUM4.5 | openssl 3.0.17-1~deb12u3 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-13836 | MEDIUM4.5 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-40777 | MEDIUM4.5 | bind9-libs 1:9.18.41-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-3592 | MEDIUM4.5 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5950 | MEDIUM4.5 | bind9-libs 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM4.5 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14831 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u6 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42015 | MEDIUM4.5 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-33948 | MEDIUM4.5 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3276 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3446 | MEDIUM4.5 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59848 | MEDIUM4.5 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-8851 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13321 | MEDIUM4.39 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13321 | MEDIUM4.39 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13321 | MEDIUM4.39 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | MEDIUM4.33 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-57432 | MEDIUM4.28 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libgssapi-krb5-2 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libk5crypto3 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5-3 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-11850 | MEDIUM4.25 | libkrb5support0 1.20.1-2+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-61145 | MEDIUM4.25 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6531 | MEDIUM4.25 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6531 | MEDIUM4.25 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6531 | MEDIUM4.25 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6531 | MEDIUM4.25 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6531 | MEDIUM4.25 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-53613 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Post-Exploit |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | — | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | — | Directly Exposed |
| CVE-2020-15719 | MEDIUM4.2 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2026-8286 | MEDIUM4.13 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8286 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8458 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15079 | MEDIUM4.13 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | MEDIUM4.13 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6100 | MEDIUM4.13 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15282 | MEDIUM4.08 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-0672 | MEDIUM4.08 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 48.2% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 48.2% High Exploitation Risk | Post-Exploit |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-1376 | MEDIUM4 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2017-14159 | MEDIUM4 | libldap-2.5-0 2.5.13+dfsg-5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-8114 | MEDIUM4 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76881 | MEDIUM4 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76882 | MEDIUM4 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76883 | MEDIUM4 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76889 | MEDIUM4 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76881 | MEDIUM4 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76882 | MEDIUM4 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76883 | MEDIUM4 | libwireshark16 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76889 | MEDIUM4 | libwireshark16 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76881 | MEDIUM4 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76882 | MEDIUM4 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76883 | MEDIUM4 | libwiretap13 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76889 | MEDIUM4 | libwiretap13 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76881 | MEDIUM4 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76882 | MEDIUM4 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76883 | MEDIUM4 | libwsutil14 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76889 | MEDIUM4 | libwsutil14 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76881 | MEDIUM4 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76882 | MEDIUM4 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76883 | MEDIUM4 | tshark 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76889 | MEDIUM4 | tshark 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48962 | LOW3.98 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5403 | LOW3.98 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5405 | LOW3.98 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5656 | LOW3.98 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11331 | LOW3.82 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11605 | LOW3.82 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11622 | LOW3.82 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11721 | LOW3.82 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12617 | LOW3.82 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13204 | LOW3.82 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11331 | LOW3.82 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11605 | LOW3.82 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11622 | LOW3.82 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11721 | LOW3.82 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12617 | LOW3.82 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13204 | LOW3.82 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11331 | LOW3.82 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11605 | LOW3.82 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11622 | LOW3.82 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-11721 | LOW3.82 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12617 | LOW3.82 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13204 | LOW3.82 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW3.82 | gzip 1.12-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-32316 | LOW3.82 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-40164 | LOW3.82 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12064 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5773 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-6276 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-8927 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8932 | LOW3.82 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58050 | LOW3.82 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27135 | LOW3.82 | nghttp2 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27135 | LOW3.82 | nghttp2-client 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27135 | LOW3.82 | nghttp2-proxy 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-27135 | LOW3.82 | nghttp2-server 1.52.0-1+deb12u2 fixed in 1.52.0-1+deb12u3 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-69421 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28388 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-28389 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-28390 | LOW3.82 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-63072 | LOW3.82 | openssl 3.0.17-1~deb12u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-54874 | LOW3.82 | openssl 3.0.17-1~deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-63074 | LOW3.82 | openssl 3.0.17-1~deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-69534 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-15308 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-3644 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-4224 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7210 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-8194 | LOW3.82 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-9781 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-1492 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-9817 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15163 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15169 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3201 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3203 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5653 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5654 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5657 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6519 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6520 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6868 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7375 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7376 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7378 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7379 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76888 | LOW3.82 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56131 | LOW3.82 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-0865 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-1502 | LOW3.82 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-4877 | LOW3.82 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-9547 | LOW3.77 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9547 | LOW3.77 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-69419 | LOW3.77 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW3.74 | libjq1 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-7256 | LOW3.74 | libpcap0.8 1.10.3-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-8006 | LOW3.74 | libpcap0.8 1.10.3-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11940 | LOW3.72 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-11940 | LOW3.72 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6069 | LOW3.65 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-8291 | LOW3.65 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-16473 | LOW3.65 | libsbc1 2.0-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-15366 | LOW3.62 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-15366 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15367 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1299 | LOW3.62 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW3.6 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4878 | LOW3.57 | libcap2-bin 1:2.66-4+deb12u2 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-1484 | LOW3.57 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u9 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | LOW3.54 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42010 | LOW3.53 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16224 | LOW3.53 | liblmdb0 0.9.24-1 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16225 | LOW3.53 | liblmdb0 0.9.24-1 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-16227 | LOW3.53 | liblmdb0 0.9.24-1 No fix yet | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-10723 | LOW3.47 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10723 | LOW3.47 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-10723 | LOW3.47 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-1965 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14819 | LOW3.47 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-25260 | LOW3.4 | libelf1 0.188-2.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-9820 | LOW3.4 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-49839 | LOW3.37 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10822 | LOW3.31 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-10822 | LOW3.31 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2016-2781 | LOW3.31 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | curl 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-10822 | LOW3.31 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-39979 | LOW3.31 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2024-23337 | LOW3.31 | jq 1.6-2.1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11856 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-3784 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5545 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6429 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-8924 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14524 | LOW3.31 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-15661 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-58051 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-66032 | LOW3.31 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW3.31 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11972 | LOW3.31 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-1801 | LOW3.31 | tcpdump 4.99.3-1 No fix yet | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-5601 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-5406 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5408 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6521 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6522 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6524 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6529 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6530 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6533 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6535 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6537 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6538 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6867 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6869 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76879 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-76928 | LOW3.31 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59846 | LOW3.31 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2018-19519 | LOW3.3 | tcpdump 4.99.3-1 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | curl 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42766 | LOW3.18 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.36-9+deb12u13 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.36-9+deb12u13 No fix yet | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31124 | LOW3.15 | libc-ares2 1.18.1-3 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.15 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0988 | LOW3.15 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u9 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5419 | LOW3.15 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0989 | LOW3.15 | libxml2 2.9.14+dfsg-1.3~deb12u4 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW3.11 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-39956 | LOW3.11 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6019 | LOW3.11 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4878 | LOW3.06 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10966 | LOW3.01 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-10966 | LOW3.01 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-66034 | LOW3.01 | libssh2-1 1.10.0-3+b1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69420 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-22796 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9669 | LOW3.01 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | libssl3 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-31789 | LOW3 | openssl 3.0.17-1~deb12u3 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5318 | LOW2.92 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-5987 | LOW2.92 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 3.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31486 | LOW2.92 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3783 | LOW2.91 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-33947 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41256 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41257 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-43894 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43896 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-44777 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-47770 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54679 | LOW2.8 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-9403 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-40612 | LOW2.8 | jq 1.6-2.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-22795 | LOW2.8 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13837 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6075 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0864 | LOW2.8 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-11596 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-11626 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13499 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13945 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-13946 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-0960 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 fixed in 4.0.17-0+deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15164 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15166 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15167 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15170 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-15171 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15172 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-15174 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5299 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5401 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5404 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5407 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-5409 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6523 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6527 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6532 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6534 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-6870 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76880 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-76917 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76918 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76923 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76924 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-9759 | LOW2.8 | wireshark-common 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-2297 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3479 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW2.8 | libpython3.11-stdlib 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0965 | LOW2.8 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.8 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-9165 | LOW2.8 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15168 | LOW2.8 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76884 | LOW2.8 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15168 | LOW2.8 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76884 | LOW2.8 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15168 | LOW2.8 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76884 | LOW2.8 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15168 | LOW2.8 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76884 | LOW2.8 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8732 | LOW2.8 | libxml2 2.9.14+dfsg-1.3~deb12u4 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15168 | LOW2.8 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76884 | LOW2.8 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW2.78 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | LOW2.75 | nghttp2 1.52.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | LOW2.75 | nghttp2-client 1.52.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | LOW2.75 | nghttp2-proxy 1.52.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-58055 | LOW2.75 | nghttp2-server 1.52.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40777 | LOW2.7 | bind9-dnsutils 1:9.18.41-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3592 | LOW2.7 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5950 | LOW2.7 | bind9-dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2025-40777 | LOW2.7 | bind9-host 1:9.18.41-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3592 | LOW2.7 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5950 | LOW2.7 | bind9-host 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | curl 7.88.1-10+deb12u14 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-40777 | LOW2.7 | dnsutils 1:9.18.41-1~deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-3592 | LOW2.7 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5950 | LOW2.7 | dnsutils 1:9.18.41-1~deb12u1 fixed in 1:9.18.49-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-33948 | LOW2.7 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-4873 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6253 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-7168 | LOW2.7 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.0.17-1~deb12u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-12084 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2025-12781 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3276 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3446 | LOW2.7 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-8277 | LOW2.63 | libssh-gcrypt-4 0.10.6-0+deb12u1 fixed in 0.10.6-0+deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-0968 | LOW2.63 | libssh-gcrypt-4 0.10.6-0+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-76885 | LOW2.63 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76887 | LOW2.63 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76891 | LOW2.63 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76885 | LOW2.63 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76887 | LOW2.63 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76891 | LOW2.63 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76885 | LOW2.63 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76887 | LOW2.63 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76891 | LOW2.63 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76885 | LOW2.63 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76887 | LOW2.63 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76891 | LOW2.63 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76885 | LOW2.63 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76887 | LOW2.63 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76891 | LOW2.63 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-4516 | LOW2.6 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-4516 | LOW2.6 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6531 | LOW2.55 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-0992 | LOW2.46 | libxml2 2.9.14+dfsg-1.3~deb12u4 fixed in 2.9.14+dfsg-1.3~deb12u6 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-10148 | LOW2.45 | curl 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | curl 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-10148 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 fixed in 7.88.1-10+deb12u15 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-14017 | LOW2.45 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-15282 | LOW2.45 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-0672 | LOW2.45 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-10536 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2025-15224 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-68160 | LOW2.4 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76881 | LOW2.4 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76882 | LOW2.4 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76883 | LOW2.4 | wireshark-common 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76889 | LOW2.4 | wireshark-common 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | curl 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-0725 | LOW2.4 | libcurl4 7.88.1-10+deb12u14 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-1485 | LOW2.38 | libglib2.0-0 2.74.6-2+deb12u7 fixed in 2.74.6-2+deb12u9 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18503 | LOW2.38 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-11468 | LOW2.29 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-11468 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-0865 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-1502 | LOW2.29 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-43895 | LOW2.24 | jq 1.6-2.1+deb12u1 fixed in 1.6-2.1+deb12u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.24 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.24 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6069 | LOW2.19 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8291 | LOW2.19 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-24515 | LOW2.12 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13978 | LOW2.12 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-8534 | LOW2.12 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW2.04 | openssl 3.0.17-1~deb12u3 fixed in 3.0.18-1~deb12u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010220 | LOW1.98 | tcpdump 4.99.3-1 No fix yet | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45446 | LOW1.89 | openssl 3.0.17-1~deb12u3 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.87 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6879 | LOW1.87 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13462 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2297 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-3479 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4519 | LOW1.68 | python3.11-minimal 3.11.2-6+deb12u6 fixed in 3.11.2-6+deb12u8 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-15168 | LOW1.68 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76884 | LOW1.68 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-11961 | LOW1.61 | libpcap0.8 1.10.3-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76885 | LOW1.58 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76887 | LOW1.58 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76891 | LOW1.58 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18503 | LOW1.43 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.12 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6879 | LOW1.12 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6020 | NONE0 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-68973 | NONE0 | gpgv 2.2.40-1.1+deb12u1 fixed in 2.2.40-1.1+deb12u2 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libncursesw6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | libtinfo6 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-base 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2023-50495 | NONE0 | ncurses-bin 6.4-4 No fix yet | 1.0% Theoretical Threat | Not Applicable |
| CVE-2026-5958 | NONE0 | sed 4.9-1 fixed in 4.9-1+deb12u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2024-22365 | NONE0 | libpam0g 1.5.2-6+deb12u1 fixed in 1.5.2-6+deb12u2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-30258 | NONE0 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-68972 | NONE0 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-modules-bin 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam-runtime 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-10041 | NONE0 | libpam0g 1.5.2-6+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login 1:4.13+dfsg1-1+deb12u1 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-3219 | NONE0 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-57062 | NONE0 | gpgv 2.2.40-1.1+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.15-2+b9 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-2219 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6297 | NONE0 | dpkg 1.21.22 fixed in 1.21.23 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-bin 2.36-9+deb12u13 No fix yet | — | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-bin 2.36-9+deb12u13 No fix yet | — | Not Applicable |
| CVE-2026-18374 | NONE0 | libc6 2.36-9+deb12u13 No fix yet | — | Not Applicable |
| CVE-2026-80489 | NONE0 | libc6 2.36-9+deb12u13 No fix yet | — | Not Applicable |
| CVE-2026-56408 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-66046 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56409 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76956 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-76957 | NONE0 | libexpat1 2.5.0-1+deb12u2 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-15806 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | libpython3.11-stdlib 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-7709 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39113 | NONE0 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-27587 | NONE0 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | libssl3 3.0.17-1~deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | libsystemd0 252.39-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-36849 | NONE0 | libtiff6 4.5.0-6+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-52491 | NONE0 | libtiff6 4.5.0-6+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-16742 | NONE0 | libudev1 252.39-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-76890 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76919 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76920 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76921 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76922 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76926 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76927 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76929 | NONE0 | libwireshark-data 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76890 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76919 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76920 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76921 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76922 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76926 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76927 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76929 | NONE0 | libwireshark16 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76890 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76919 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76920 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76921 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76922 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76926 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76927 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76929 | NONE0 | libwiretap13 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76890 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76919 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76920 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76921 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76922 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76926 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76927 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76929 | NONE0 | libwsutil14 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login 1:4.13+dfsg1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2025-27587 | NONE0 | openssl 3.0.17-1~deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-75803 | NONE0 | openssl 3.0.17-1~deb12u3 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.13+dfsg1-1+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.11 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-15806 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-17084 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-19672 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-8328 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-12003 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15310 | NONE0 | python3.11-minimal 3.11.2-6+deb12u6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.06-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Not Applicable |
| CVE-2026-76890 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76919 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76920 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76921 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76922 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76926 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76927 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76929 | NONE0 | tshark 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | — | Not Applicable |
| CVE-2026-76890 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76919 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76920 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76921 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76922 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76926 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-76927 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-76929 | NONE0 | wireshark-common 4.0.17-0+deb12u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.