Last scanned:
··This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The main concern is CVE-2026-95619 in the C++ runtime libraries that Node loads, which could lead to memory corruption if attacker-controlled sizes reach the affected code path. The scan's highest-severity findings are moderate, none are known to be actively exploited, and the scan states no special configuration is required for the main concern to apply. Updating the Debian base packages to a patched release is the practical way to close these findings, and the image's official, digest-pinned origin supports that upgrade path.
Hardening plan for this image · 4 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-95619 | MEDIUM6.16 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 0.4% 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-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-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-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-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-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-78409 | MEDIUM4.2 | libblkid1 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-78409 | MEDIUM4.2 | libsmartcols1 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-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-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-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-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-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+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-104844 | LOW3.54 | postcss-selector-parser 7.1.1 fixed in 7.1.6, 6.1.5 | 0.4% 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~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-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~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-2026-48758 | LOW3.24 | @sigstore/core 2.0.0 fixed in 3.2.1 | 0.2% Theoretical Threat | Post-Exploit |
| 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-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-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-2026-16742 | LOW3.17 | libsystemd0 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libudev1 252.39-1~deb12u2 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-69192 | LOW3.1 | ip-address 10.1.0 fixed in 10.3.1 | 0.5% 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-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-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-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-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-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~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-2026-102276 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-102278 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-14257 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-69152 | LOW2.7 | brace-expansion 2.0.2 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-33750 | LOW2.7 | brace-expansion 2.0.2 fixed in 5.0.5, 3.0.2, 2.0.3, 1.1.13 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-93748 | LOW2.7 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 19.0.2 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 20.0.1 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33671 | LOW2.7 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48815 | LOW2.7 | sigstore 3.1.0 fixed in 4.1.1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56851 | LOW2.7 | golang.org/x/text v0.38.0 fixed in 0.41.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-56852 | LOW2.7 | golang.org/x/text v0.38.0 fixed in 0.39.0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2022-27943 | LOW2.65 | gcc-12-base 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-27943 | LOW2.65 | libgcc-s1 12.2.0-14+deb12u1 No fix yet | 1.0% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2022-27943 | LOW2.65 | libstdc++6 12.2.0-14+deb12u1 No fix yet | 1.0% 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-2026-9358 | LOW2.58 | postcss-selector-parser 7.1.1 fixed in 6.1.3, 7.1.3 | 0.3% 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-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-86805 | LOW2.52 | libc-bin 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | libc-bin 2.36-9+deb12u14 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | libc6 2.36-9+deb12u14 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-95818 | LOW2.52 | libc6 2.36-9+deb12u14 No fix yet | 0.1% 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-53613 | 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-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-2026-19499 | LOW2.45 | libc-bin 2.36-9+deb12u14 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-19499 | LOW2.45 | libc6 2.36-9+deb12u14 No fix yet | 0.3% 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.1.0 fixed in 0.44.0 | 0.1% 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-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-2025-14104 | LOW2.34 | libmount1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.2% Theoretical Threat | 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-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-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-42338 | LOW2.2 | ip-address 10.1.0 fixed in 10.1.1 | 0.5% Theoretical Threat | 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-13151 | LOW2.12 | libtasn1-6 4.19.0-2+deb12u1 No fix yet | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| 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-0563 | LOW1.99 | libblkid1 2.38.1-5+deb12u3 No fix yet | 0.4% 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-0563 | LOW1.99 | libsmartcols1 2.38.1-5+deb12u3 No fix yet | 0.4% 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-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-27171 | LOW1.98 | zlib1g 1:1.2.13.dfsg-1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13149 | LOW1.91 | brace-expansion 2.0.2 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-102277 | LOW1.91 | brace-expansion 2.0.2 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101911 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101912 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-101913 | LOW1.91 | ip-address 10.1.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-111997 | LOW1.91 | ip-address 10.1.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-33672 | LOW1.91 | picomatch 4.0.3 fixed in 4.0.4, 3.0.2, 2.3.2 | 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+deb12u7 No fix yet | 73.3% Actively Exploited | 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-41991 | LOW1.69 | gzip 1.12-1 No fix yet | 0.1% 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+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-2026-82560 | LOW1.44 | perl-base 5.36.0-7+deb12u4 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-67693 | LOW1.4 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88647 | LOW1.4 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-88648 | LOW1.4 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95184 | LOW1.4 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-31486 | LOW1.4 | perl-base 5.36.0-7+deb12u4 No fix yet | 1.7% Low-Moderate Risk | 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+deb12u4 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-95209 | LOW0.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-95210 | LOW0.9 | libgnutls30 3.7.9-2+deb12u7 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-68121 | NONE0 | stdlib v1.24.6 fixed in 1.24.13, 1.25.7, 1.26.0-rc.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 1.8% Low-Moderate Risk | Not Applicable |
| CVE-2026-39821 | NONE0 | stdlib v1.26.4 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.24.6 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-56858 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.24.6 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-39822 | NONE0 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-61726 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 2.3% Low-Moderate Risk | Not Applicable |
| CVE-2025-61729 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-25679 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-27145 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32280 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-32281 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32283 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-33811 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-33814 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.24.6 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.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-39836 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42499 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.8% Theoretical Threat | Not Applicable |
| CVE-2026-42504 | NONE0 | stdlib v1.24.6 fixed in 1.25.11, 1.26.4 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.24.6 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.24.6 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.24.6 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.24.6 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.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58183 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58188 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61728 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-33818 | NONE0 | stdlib v1.26.4 fixed in 1.25.13, 1.26.6, 1.27.0-rc.3 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-46600 | NONE0 | stdlib v1.26.4 fixed in 1.26.6, 1.27.0-rc.3 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-56853 | NONE0 | stdlib v1.26.4 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.26.4 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.26.4 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.26.4 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.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78669 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-97031 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-78659 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-78660 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-94440 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.24.6 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-111943 | NONE0 | stdlib v1.26.4 fixed in 1.26.10, 1.27.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-61727 | NONE0 | stdlib v1.24.6 fixed in 1.24.11, 1.25.5 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39825 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-56866 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-94439 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-32282 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-32289 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-94448 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97030 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-97032 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2026-32288 | NONE0 | stdlib v1.24.6 fixed in 1.25.9, 1.26.2 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27142 | NONE0 | stdlib v1.24.6 fixed in 1.25.8, 1.26.1 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-39823 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-39826 | NONE0 | stdlib v1.24.6 fixed in 1.25.10, 1.26.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-47912 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-58185 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58187 | NONE0 | stdlib v1.24.6 fixed in 1.24.9, 1.25.3 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-58189 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.5% Theoretical Threat | Not Applicable |
| CVE-2025-61723 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.7% Theoretical Threat | Not Applicable |
| CVE-2025-61724 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61725 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-61730 | NONE0 | stdlib v1.24.6 fixed in 1.24.12, 1.25.6 | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.24.6 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.24.6 fixed in 1.25.11, 1.26.4 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2025-58186 | NONE0 | stdlib v1.24.6 fixed in 1.24.8, 1.25.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-42505 | NONE0 | stdlib v1.26.4 fixed in 1.25.12, 1.26.5, 1.27.0-rc.2 | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-78663 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.24.6 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-56857 | NONE0 | stdlib v1.26.4 fixed in 1.26.9, 1.27.2 | 0.6% Theoretical Threat | Not Applicable |
| CVE-2026-27139 | NONE0 | stdlib v1.24.6 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.