Last scanned:
··This image is safe for production use. The scan found vulnerabilities, but none of the reachable ones is rated high or is known to be actively exploited, so they do not drive the verdict. The more relevant risk is the default configuration, which accepts connections from any client that can reach the Redis port without a password. Enabling authentication and protected mode before deployment, and keeping the port restricted to trusted networks, will address the most practical exposure.
Already in good shape · 5 hardening steps left
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15281 | MEDIUM5.9 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-31790 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5.88 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-0915 | MEDIUM5.3 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | 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+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.36-9+deb12u13 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-29111 | MEDIUM4.68 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM4.68 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-28388 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-28389 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-28390 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.36-9+deb12u13 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | LOW3.9 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | LOW3.9 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.36-9+deb12u13 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libsystemd0 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libudev1 252.39-1~deb12u1 fixed in 252.39-1~deb12u2 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg6.0 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.36-9+deb12u13 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.22-1~deb12u1 | 0.3% Theoretical Threat | Directly Exposed |
| 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-2026-8376 | LOW3.53 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-45853 | LOW3.53 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 3.4% Low-Moderate Risk | Post-Exploit |
| CVE-2023-31437 | LOW3.31 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 252.39-1~deb12u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-61801 | LOW3.3 | github.com/moby/sys/user v0.1.0 fixed in 0.4.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW3.3 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 252.39-1~deb12u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-33845 | LOW3.28 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 2.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | LOW3.28 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.20-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW3.28 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libsystemd0 252.39-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libudev1 252.39-1~deb12u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-2219 | LOW3 | dpkg 1.21.22 fixed in 1.21.23 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42013 | LOW2.95 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-5260 | LOW2.95 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-86145 | LOW2.95 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | LOW2.92 | libc-bin 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-0861 | LOW2.92 | libc6 2.36-9+deb12u13 fixed in 2.36-9+deb12u14 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-28387 | LOW2.92 | libssl3 3.0.18-1~deb12u2 fixed in 3.0.19-1~deb12u2 | 0.7% Theoretical Threat | Post-Exploit |
| 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 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libuuid1 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 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libuuid1 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-2025-68972 | LOW2.82 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| 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-2026-76642 | LOW2.81 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.81 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% 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 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% 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-48962 | LOW2.81 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.4% 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-2013-4392 | LOW2.8 | libsystemd0 252.39-1~deb12u1 No fix yet | 0.5% 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-95619 | LOW2.77 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-95619 | LOW2.77 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-103111 | LOW2.74 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.12-1 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-41989 | LOW2.7 | libgcrypt20 1.10.1-3 fixed in 1.10.1-3+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-33846 | LOW2.7 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42009 | LOW2.7 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42497 | LOW2.7 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW2.7 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-3833 | LOW2.66 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42011 | LOW2.66 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.66 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| 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-2026-54369 | LOW2.56 | libacl1 2.3.1-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42012 | LOW2.56 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-4878 | LOW2.52 | libcap2 1:2.66-4+deb12u2+b2 fixed in 1:2.66-4+deb12u3 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102010 | LOW2.52 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libuuid1 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-78409 | 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-78409 | 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-78409 | LOW2.52 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-30258 | LOW2.4 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-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-39824 | LOW2.4 | golang.org/x/sys v0.13.0 fixed in 0.44.0 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-42014 | LOW2.38 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW2.34 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW2.34 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | libtinfo6 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-base 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-50495 | LOW2.34 | ncurses-bin 6.4-4 No fix yet | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-15649 | LOW2.34 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.4% Theoretical Threat | Post-Exploit |
| 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-2005-2541 | LOW2.34 | tar 1.34+dfsg-1.2+deb12u1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-54370 | LOW2.27 | libacl1 2.3.1-3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54371 | LOW2.27 | libattr1 1:2.5.1-4 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-13757 | LOW2.23 | libp11-kit0 0.24.1-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18938 | LOW2.23 | libp11-kit0 0.24.1-2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 2.6.1 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-105712 | LOW2.16 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89156 | LOW2.12 | libpcre2-8-0 10.42-1 fixed in 10.42-1+deb12u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-13151 | LOW2.12 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2025-27587 | LOW2.12 | libssl3 3.0.18-1~deb12u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-15534 | LOW2.05 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-2007-5686 | LOW1.99 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-27171 | LOW1.98 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-14831 | LOW1.91 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u6 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-42015 | LOW1.91 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-34743 | LOW1.91 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | mount 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW1.91 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.13+dfsg1-1+deb12u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-3389 | LOW1.82 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 73.3% Actively Exploited | Post-Exploit |
| CVE-2026-48959 | LOW1.8 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-7010 | LOW1.8 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7017 | LOW1.8 | perl-base 5.36.0-7+deb12u3 fixed in 5.36.0-7+deb12u4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-85091 | LOW1.8 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.5% 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-2026-27456 | LOW1.69 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW1.69 | gzip 1.12-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-3219 | LOW1.68 | gpgv 2.2.40-1.1+deb12u2 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.15-2+b10 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-9820 | LOW1.44 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u6 | 0.2% Theoretical Threat | Post-Exploit |
| DLA-4783-1 | LOW1.44 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u2 | — | Post-Exploit |
| TEMP-1147318-639065 | LOW1.44 | liblzma5 5.4.1-1 fixed in 5.4.1-1+deb12u2 | — | Post-Exploit |
| CVE-2026-82560 | LOW1.44 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2018-6829 | LOW1.4 | libgcrypt20 1.10.1-3 No fix yet | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2236 | LOW1.4 | libgcrypt20 1.10.1-3 No fix yet | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-67693 | LOW1.4 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88647 | LOW1.4 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88648 | LOW1.4 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95184 | LOW1.4 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | mount 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | LOW1.4 | perl-base 5.36.0-7+deb12u3 No fix yet | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5419 | LOW1.33 | libgnutls30 3.7.9-2+deb12u5 fixed in 3.7.9-2+deb12u7 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6297 | LOW1.27 | dpkg 1.21.22 fixed in 1.21.23 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | bsdutils 1:2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW1.19 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libuuid1 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | mount 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | util-linux 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | util-linux-extra 2.38.1-5+deb12u3 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libtinfo6 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-base 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-bin 6.4-4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.01 | perl-base 5.36.0-7+deb12u3 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-95209 | LOW0.9 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95210 | LOW0.9 | libgnutls30 3.7.9-2+deb12u5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.18.2 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-24538 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-24540 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2024-24790 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-22871 | NONE0 | stdlib v1.18.2 fixed in 1.23.8, 1.24.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2022-30580 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2023-29403 | NONE0 | stdlib v1.18.2 fixed in 1.19.10, 1.20.5 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-27664 | NONE0 | stdlib v1.18.2 fixed in 1.18.6, 1.19.1 | 3.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-28131 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-2879 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 2.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-2880 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-29804 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 2.4% Low-Moderate Risk | Not Applicable |
| CVE-2022-30630 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30631 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30632 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30633 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 2.2% Low-Moderate Risk | Not Applicable |
| CVE-2022-30634 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-30635 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2022-32189 | NONE0 | stdlib v1.18.2 fixed in 1.17.13, 1.18.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2022-41715 | NONE0 | stdlib v1.18.2 fixed in 1.18.7, 1.19.2 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41716 | NONE0 | stdlib v1.18.2 fixed in 1.18.8, 1.19.3 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2022-41720 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2022-41722 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.7% Low-Moderate Risk | Not Applicable |
| CVE-2022-41723 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 4.6% Low-Moderate Risk | Not Applicable |
| CVE-2022-41724 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2022-41725 | NONE0 | stdlib v1.18.2 fixed in 1.19.6, 1.20.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-24534 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.9% Low-Moderate Risk | Not Applicable |
| CVE-2023-24536 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-24537 | NONE0 | stdlib v1.18.2 fixed in 1.19.8, 1.20.3 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2023-39325 | NONE0 | stdlib v1.18.2 fixed in 1.20.10, 1.21.3 | 3.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45283 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4, 1.20.12, 1.21.5 | 2.8% Low-Moderate Risk | Not Applicable |
| CVE-2023-45287 | NONE0 | stdlib v1.18.2 fixed in 1.20.0 | 1.3% Low-Moderate Risk | Not Applicable |
| CVE-2023-45288 | NONE0 | stdlib v1.18.2 fixed in 1.21.9, 1.22.2 | 92.0% Actively Exploited | Not Applicable |
| CVE-2024-34156 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-39820 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56859 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56860 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56862 | NONE0 | stdlib v1.18.2 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78667 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2023-24539 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2023-29400 | NONE0 | stdlib v1.18.2 fixed in 1.19.9, 1.20.4 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2025-47907 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.18.2 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-4673 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2022-1705 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2022-32148 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2023-29406 | NONE0 | stdlib v1.18.2 fixed in 1.19.11, 1.20.6 | 1.5% Low-Moderate Risk | Not Applicable |
| CVE-2024-24785 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2025-47906 | NONE0 | stdlib v1.18.2 fixed in 1.23.12, 1.24.6 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.18.2 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% 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-2023-39318 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-39319 | NONE0 | stdlib v1.18.2 fixed in 1.20.8, 1.21.1 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24783 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2024-24791 | NONE0 | stdlib v1.18.2 fixed in 1.21.12, 1.22.5 | 1.4% Low-Moderate Risk | Not Applicable |
| CVE-2024-34155 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2024-34158 | NONE0 | stdlib v1.18.2 fixed in 1.22.7, 1.23.1 | 1.0% Low-Moderate Risk | Not Applicable |
| CVE-2024-45336 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2022-1962 | NONE0 | stdlib v1.18.2 fixed in 1.17.12, 1.18.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2024-24789 | NONE0 | stdlib v1.18.2 fixed in 1.21.11, 1.22.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-0913 | NONE0 | stdlib v1.18.2 fixed in 1.23.10, 1.24.4 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.18.2 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2024-24784 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.18.2 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2022-41717 | NONE0 | stdlib v1.18.2 fixed in 1.18.9, 1.19.4 | 6.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-24532 | NONE0 | stdlib v1.18.2 fixed in 1.19.7, 1.20.2 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2023-29409 | NONE0 | stdlib v1.18.2 fixed in 1.19.12, 1.20.7, 1.21.0-rc.4 | 1.6% Low-Moderate Risk | Not Applicable |
| CVE-2023-39326 | NONE0 | stdlib v1.18.2 fixed in 1.20.12, 1.21.5 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2023-45284 | NONE0 | stdlib v1.18.2 fixed in 1.20.11, 1.21.4 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2023-45289 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.1% Low-Moderate Risk | Not Applicable |
| CVE-2023-45290 | NONE0 | stdlib v1.18.2 fixed in 1.21.8, 1.22.1 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2025-22866 | NONE0 | stdlib v1.18.2 fixed in 1.22.12, 1.23.6, 1.24.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2025-22873 | NONE0 | stdlib v1.18.2 fixed in 1.23.9, 1.24.3 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.18.2 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.18.2 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.18.2 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-42507 | NONE0 | stdlib v1.18.2 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.18.2 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-22870 | NONE0 | stdlib v1.18.2 fixed in 1.23.7, 1.24.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2024-45341 | NONE0 | stdlib v1.18.2 fixed in 1.22.11, 1.23.5, 1.24.0-rc.2 | 0.6% Theoretical Threat | Not Applicable |
| DLA-4792-1 | NONE0 | tzdata 2025b-0+deb12u2 fixed in 2026c-0+deb12u1 | — | Not Applicable |
| DLA-4854-1 | NONE0 | tzdata 2025b-0+deb12u2 fixed in 2026e-0+deb12u1 | — | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.18.2 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2022-30629 | NONE0 | stdlib v1.18.2 fixed in 1.17.11, 1.18.3 | 1.2% Low-Moderate Risk | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.18.2 fixed in 1.25.8, 1.26.1 | 0.2% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.