Last scanned:
··This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The most significant items are libxml2 flaws, CVE-2026-6653 and CVE-2026-86138, which the scan rates as conditional: they apply only when the system libxml2 library parses untrusted XML, a non-default setup that the scan could not confirm for this image. Other exposed findings in libtiff and Python carry a severity of 6.0 and are similarly tied to specific features or code paths. Updating the libxml2 and libtiff packages in a rebuilt image is the most direct way to reduce this exposure.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-6653 | HIGH7.84 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86138 | MEDIUM6.24 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-52355 | MEDIUM6 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-3644 | MEDIUM6 | python 3.11.18 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-7210 | MEDIUM6 | python 3.11.18 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-113351 | MEDIUM5.9 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-45853 | MEDIUM5.88 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-12912 | MEDIUM5.84 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-52490 | MEDIUM5.84 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86143 | MEDIUM5.84 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-115567 | MEDIUM5.8 | tokio 1.54.0 fixed in 1.54.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-5388 | MEDIUM5.52 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-7531 | MEDIUM5.52 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-39329 | MEDIUM5.52 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-66382 | MEDIUM5.5 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95512 | MEDIUM5.5 | libfreetype6 2.12.1+dfsg-5+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13837 | MEDIUM5.5 | python 3.11.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58016 | MEDIUM5.46 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-12084 | MEDIUM5.3 | python 3.11.18 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-12781 | MEDIUM5.3 | python 3.11.18 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-6277 | MEDIUM5.2 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-58014 | MEDIUM5.16 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-74860 | MEDIUM5.1 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2011-3389 | MEDIUM5.07 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 73.3% Actively Exploited | Directly Exposed |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-5+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | MEDIUM4.98 | libxrender-dev 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-88807 | MEDIUM4.98 | libxrender1 1:0.9.10-1.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-58010 | MEDIUM4.92 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58012 | MEDIUM4.92 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58013 | MEDIUM4.92 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18495 | MEDIUM4.88 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11822 | MEDIUM4.68 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-11824 | MEDIUM4.68 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86140 | MEDIUM4.68 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86142 | MEDIUM4.68 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86144 | MEDIUM4.68 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-39328 | MEDIUM4.67 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-10911 | MEDIUM4.67 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-7458 | MEDIUM4.64 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-58011 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-58015 | MEDIUM4.5 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-36849 | MEDIUM4.5 | libtiff6 4.5.0-6+deb12u4 No fix yet | — | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88806 | MEDIUM4.5 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76781 | MEDIUM4.4 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-16118 | MEDIUM4.26 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-115506 | MEDIUM4 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107080 | MEDIUM4 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107778 | LOW3.9 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libncursesw6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-93311 | LOW3.9 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-85231 | LOW3.9 | libtirpc3 1.3.3+ds-1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94283 | LOW3.9 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-50495 | LOW3.9 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-93311 | LOW3.9 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-7475 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2018-18064 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6461 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6462 | LOW3.9 | libcairo2 1.16.0-7 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2018-6829 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2236 | LOW3.9 | libgcrypt20 1.10.1-3+deb12u1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-67693 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88647 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-88648 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95184 | LOW3.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-9937 | LOW3.9 | libjbig0 2.1-6.1 No fix yet | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2016-10505 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9113 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9114 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9115 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9116 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.2% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9117 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9580 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2016-9581 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2018-16376 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-6988 | LOW3.9 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-28162 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-28164 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-3713 | LOW3.9 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2015-9019 | LOW3.9 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-93313 | LOW3.78 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-93314 | LOW3.78 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-93313 | LOW3.78 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-93314 | LOW3.78 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13757 | LOW3.72 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-18938 | LOW3.72 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.2 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-41080 | LOW3.7 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-59890 | LOW3.66 | setuptools 79.0.1 fixed in 83.0.0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-6019 | LOW3.66 | python 3.11.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-6135 | LOW3.65 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-39327 | LOW3.65 | libopenjp2-7 2.5.0-2+deb12u3 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-13151 | LOW3.54 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6357 | LOW3.48 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW3.42 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | LOW3.31 | libexpat1 2.5.0-1+deb12u5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-11695 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11696 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2017-11697 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2017-11698 | LOW3.31 | libnss3 2:3.87.1-1+deb12u4 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-37769 | LOW3.31 | libpixman-1-0 0.42.2-1 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-4214 | LOW3.31 | libpng16-16 1.6.39-2+deb12u6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 252.39-1~deb12u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-107705 | LOW3.3 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93653 | LOW3.3 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50812 | LOW3.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-50813 | LOW3.3 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94284 | LOW3.3 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107705 | LOW3.3 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93653 | LOW3.3 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW3.3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8643 | LOW3.3 | pip 24.0 fixed in 26.1.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-24049 | LOW3.3 | wheel 0.45.1 fixed in 0.46.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW3.3 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 252.39-1~deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-13462 | LOW3.3 | python 3.11.18 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-4519 | LOW3.3 | python 3.11.18 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15588 | LOW3.18 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-86469 | LOW3.18 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc-common 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85977 | LOW3.18 | libtirpc3 1.3.3+ds-1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2017-16232 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 5.4% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2018-10126 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2022-1210 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 1.8% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-61143 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-61144 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-61145 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-52491 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-52492 | LOW3.12 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11979 | LOW3.12 | libxml2 2.9.14+dfsg-1.3~deb12u6 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-23949 | LOW3.1 | jaraco.context 5.3.0 fixed in 6.1.0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-94285 | LOW3.06 | libx11-6 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-data 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-94285 | LOW3.06 | libx11-dev 2:1.8.4-2+deb12u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | LOW3 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-3219 | LOW3 | pip 24.0 fixed in 26.1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-107708 | LOW2.94 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.82 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68972 | LOW2.82 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.82 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libncursesw6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.4-4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-50422 | LOW2.8 | libcairo2 1.16.0-7 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 252.39-1~deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-41992 | LOW2.7 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-8869 | LOW2.7 | pip 24.0 fixed in 25.3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1916 | LOW2.65 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-3164 | LOW2.65 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2023-6228 | LOW2.65 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-8176 | LOW2.65 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-8177 | LOW2.65 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-8851 | LOW2.65 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18477 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-11731 | LOW2.63 | libxslt1.1 1.1.35-1+deb12u4 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-93312 | LOW2.58 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-93312 | LOW2.58 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-7709 | LOW2.55 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | LOW2.52 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95209 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | — | Directly Exposed |
| CVE-2026-95210 | LOW2.5 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-modules-bin 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam-runtime 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-10041 | LOW2.4 | libpam0g 1.5.2-6+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-82560 | LOW2.4 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13346 | LOW2.34 | pip 24.0 fixed in 26.2.0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-56391 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.1-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.8-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2012-0039 | LOW2.34 | libglib2.0-0 2.74.6-2+deb12u9 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2018-5709 | LOW2.34 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-26461 | LOW2.34 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-11850 | LOW2.34 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2017-2814 | LOW2.34 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-2818 | LOW2.34 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-2820 | LOW2.34 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9083 | LOW2.34 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9543 | LOW2.34 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9545 | LOW2.34 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW2.34 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31486 | LOW2.34 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2017-2814 | LOW2.34 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 3.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-2818 | LOW2.34 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2017-2820 | LOW2.34 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 4.4% Low-Moderate Risk | Directly Exposed |
| CVE-2017-9083 | LOW2.34 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9543 | LOW2.34 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9545 | LOW2.34 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 1.9% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-1703 | LOW2.34 | pip 24.0 fixed in 26.0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-8961 | LOW2.24 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-9165 | LOW2.24 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2011-3374 | LOW2.22 | apt 2.6.2 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-29070 | LOW2.12 | liblcms2-2 2.14-2+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-27587 | LOW2.12 | libssl3 3.0.22-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2016-2781 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.1-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.99 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libgssapi-krb5-2 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libk5crypto3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5-3 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-26458 | LOW1.99 | libkrb5support0 1.20.1-2+deb12u5 No fix yet | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-24106 | LOW1.99 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-29088 | LOW1.99 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2022-27943 | LOW1.99 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-24106 | LOW1.99 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-102620 | LOW1.98 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102621 | LOW1.98 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-70873 | LOW1.98 | libsqlite3-0 3.40.1-2+deb12u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-102620 | LOW1.98 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-102621 | LOW1.98 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-57062 | LOW1.74 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-13978 | LOW1.7 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-8534 | LOW1.7 | libtiff6 4.5.0-6+deb12u4 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.68 | libncursesw6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4472 | LOW1.68 | libpoppler126 22.12.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4472 | LOW1.68 | poppler-utils 22.12.0-2+deb12u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.15-2+b13 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.06-4 No fix yet | — | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | — | Post-Exploit |
| CVE-2025-27587 | LOW1.27 | openssl 3.0.22-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| GHSA-xmj3-9gf7-h52w | LOW0.6 | setuptools 79.0.1 fixed in 84.1.0 | — | Directly Exposed |
| CVE-2026-86805 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-86805 | NONE0 | locales 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Not Applicable |
| CVE-2026-95818 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-19499 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6238 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5435 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-6791 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-77117 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-80489 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-6368 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-8674 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-5450 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-5928 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-18374 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-19542 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-89092 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2010-4756 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2010-4756 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2018-20796 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 5.8% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010022 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010023 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 3.1% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010024 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 3.2% Low-Moderate Risk | Not Applicable |
| CVE-2019-1010025 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 2.5% Low-Moderate Risk | Not Applicable |
| CVE-2019-9192 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2026-97399 | NONE0 | libc-l10n 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97399 | NONE0 | locales 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.