Last scanned:
This base/runtime image is a reasonable foundation, but it ships vulnerabilities worth remediating in the images built on top of it. The most significant inherited issues are medium-severity flaws whose exposure depends on how applications use them, such as CVE-2026-69192 in SSRF filtering. CVE-2026-58043 only matters if the Node.js permission model is enabled, and CVE-2026-18798 only matters if a QUIC server is run, so many findings may not apply to a given deployment. Because the image runs as root by default, downstream images should be reviewed for these conditions and rebuilt on a patched base when updates are available. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-69192 | MEDIUM6.88 | ip-address 10.2.0 fixed in 10.3.1 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-58043 | MEDIUM6.72 | node 24.18.0 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95619 | MEDIUM6.16 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18798 | MEDIUM6 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18798 | MEDIUM6 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102276 | MEDIUM6 | brace-expansion 5.0.6 fixed in 5.0.10, 3.0.7, 2.1.5, 1.1.19 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102278 | MEDIUM6 | brace-expansion 5.0.6 fixed in 5.0.11, 3.0.8, 2.1.6, 1.1.20 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14257 | MEDIUM6 | brace-expansion 5.0.6 fixed in 5.0.8, 3.0.3, 2.1.3, 1.1.17 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69152 | MEDIUM6 | brace-expansion 5.0.6 fixed in 1.1.18, 2.1.4, 3.0.6, 5.0.9 | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93748 | MEDIUM6 | http-cache-semantics 4.2.0 No fix yet | 0.6% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-109869 | MEDIUM6 | undici 6.26.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-12151 | MEDIUM6 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.8% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-19534 | MEDIUM6 | undici 6.26.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54872 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54272 | MEDIUM5.76 | ip-address 10.2.0 fixed in 10.2.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102010 | MEDIUM5.6 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM5.5 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-16728 | MEDIUM5.2 | undici 6.26.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-16729 | MEDIUM5.2 | undici 6.26.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42250 | MEDIUM5 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc-bin 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.41-12+deb13u3 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-85091 | MEDIUM5 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-85024 | MEDIUM4.72 | undici 6.26.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-9679 | MEDIUM4.72 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54875 | MEDIUM4.7 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54875 | MEDIUM4.7 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-109924 | MEDIUM4.5 | undici 6.26.0 fixed in 6.29.1, 7.30.1, 8.12.2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-56850 | MEDIUM4.4 | node 24.18.0 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-15157 | MEDIUM4.32 | undici 6.26.0 fixed in 6.28.0, 7.29.0, 8.9.0 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-13149 | MEDIUM4.24 | brace-expansion 5.0.6 fixed in 5.0.7, 1.1.16, 2.1.2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-102277 | MEDIUM4.24 | brace-expansion 5.0.6 fixed in 5.0.12, 3.0.9, 2.1.7, 1.1.21 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101910 | MEDIUM4.24 | ip-address 10.2.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101911 | MEDIUM4.24 | ip-address 10.2.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101912 | MEDIUM4.24 | ip-address 10.2.0 fixed in 10.7.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-101913 | MEDIUM4.24 | ip-address 10.2.0 fixed in 10.5.1 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-111997 | MEDIUM4.24 | ip-address 10.2.0 fixed in 10.7.4 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-69198 | MEDIUM4.24 | ip-address 10.2.0 fixed in 10.2.2 | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.41-12+deb13u3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.41-12+deb13u3 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| DSA-6549-1 | MEDIUM4 | liblzma5 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| TEMP-1147318-639065 | MEDIUM4 | liblzma5 5.8.1-1+deb13u1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.41-12+deb13u3 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc-bin 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.41-12+deb13u3 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3t64 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-provider-legacy 3.5.6-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-56847 | LOW3.66 | node 24.18.0 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-8376 | LOW3.53 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2023-31437 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 257.13-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 257.13-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13221 | LOW3.28 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW3.28 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libsystemd0 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-16742 | LOW3.17 | libudev1 257.13-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-57432 | LOW3.02 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11525 | LOW2.96 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-18540 | LOW2.96 | undici 6.26.0 fixed in 6.28.1, 7.29.1, 8.10.2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-6733 | LOW2.96 | undici 6.26.0 fixed in 6.27.0, 7.28.0, 8.5.0 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-86145 | LOW2.95 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53615 | LOW2.88 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54411 | LOW2.88 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78408 | LOW2.84 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89161 | LOW2.81 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-11822 | LOW2.81 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-11824 | LOW2.81 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-base 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | LOW2.81 | ncurses-bin 6.5+20250216-2 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-48962 | LOW2.81 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-76642 | LOW2.81 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-78410 | LOW2.81 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.13-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-103111 | LOW2.74 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.7 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW2.7 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-57433 | LOW2.7 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9496 | LOW2.7 | pacote 21.5.0 fixed in 21.5.1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-59873 | LOW2.7 | tar 7.5.15 fixed in 7.5.19 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-59874 | LOW2.7 | tar 7.5.15 fixed in 7.5.18 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-73566 | LOW2.7 | tar 7.5.15 fixed in 7.5.21 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-59871 | LOW2.7 | tar 7.5.15 fixed in 7.5.18 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-89157 | LOW2.66 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54369 | LOW2.56 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | libc-bin 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-86805 | LOW2.52 | libc6 2.41-12+deb13u3 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53612 | LOW2.52 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53613 | LOW2.52 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-53614 | LOW2.52 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-78409 | LOW2.52 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89158 | LOW2.34 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-89160 | LOW2.34 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-15649 | LOW2.34 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-19487 | LOW2.34 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.34 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-102473 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-102474 | LOW2.34 | dash 0.5.12-12 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.34 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-54370 | LOW2.27 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-54371 | LOW2.27 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-89156 | LOW2.12 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-104844 | LOW2.12 | postcss-selector-parser 7.1.1 fixed in 7.1.6, 6.1.5 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-15534 | LOW2.05 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW1.99 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-50812 | LOW1.98 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-50813 | LOW1.98 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW1.98 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53655 | LOW1.98 | tar 7.5.15 fixed in 7.5.16 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW1.91 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW1.91 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW1.91 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-59875 | LOW1.91 | tar 7.5.15 fixed in 7.5.17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2024-56433 | LOW1.84 | passwd 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW1.8 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW1.8 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-7010 | LOW1.8 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-7017 | LOW1.8 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW1.69 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW1.69 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW1.58 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW1.58 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-9358 | LOW1.55 | postcss-selector-parser 7.1.1 fixed in 6.1.3, 7.1.3 | 0.3% Theoretical Threat | Post-Exploit |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.37-2+b9 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | login.defs 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0628843-DBAD28 | LOW1.5 | passwd 1:4.17.4-2 No fix yet | — | Post-Exploit |
| TEMP-0517018-A83CE6 | LOW1.5 | sysvinit-utils 3.14-4 No fix yet | — | Post-Exploit |
| CVE-2026-82560 | LOW1.44 | perl-base 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | bsdutils 1:2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libblkid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | liblastlog2-2 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libmount1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libsmartcols1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2021-45346 | LOW1.4 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | libuuid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | mount 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2005-2541 | LOW1.4 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW1.4 | util-linux 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.19 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-89162 | LOW1.19 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW1.19 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-6141 | LOW1.01 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2011-4116 | LOW1.01 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| TEMP-0290435-0B57B5 | LOW0.9 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.