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 notable exposure is CVE-2026-54369 in libacl1 (severity 6.03), which could allow local privilege escalation through symlink traversal; however, it requires local access and is not remotely exploitable. All other exposed findings and post-exploit findings are below severity 7.0 (post max 3.98), so they pose minimal practical risk. Since this is a base image, applying security updates in derived images will eliminate these inherited issues. 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-54369 | MEDIUM6.03 | libacl1 2.3.2-2+b1 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM5.95 | libcap2 1:2.75-10+b8 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42764 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM5.7 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.52 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | MEDIUM5.52 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12+deb13u2 No fix yet | — | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | MEDIUM5.44 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | MEDIUM5.44 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | MEDIUM5.35 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | MEDIUM5.35 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | MEDIUM5.35 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc-bin 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | MEDIUM5.3 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | MEDIUM5.3 | libc6 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libblkid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | liblastlog2-2 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libmount1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libsmartcols1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | MEDIUM5.18 | libuuid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.02 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | MEDIUM4.67 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-27171 | MEDIUM4.67 | zlib1g 1:1.3.dfsg+really1.3.1-1+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM4.5 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | MEDIUM4.5 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | MEDIUM4.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | MEDIUM4.5 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | MEDIUM4.5 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | MEDIUM4.3 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42250 | MEDIUM4.25 | libbz2-1.0 1.0.8-6 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc-bin 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM4.25 | libc6 2.41-12+deb13u2 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM4.25 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | MEDIUM4 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc-bin 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-48962 | LOW3.98 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-42497 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-9538 | LOW3.82 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW3.77 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2011-3374 | LOW3.7 | libapt-pkg7.0 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2005-2541 | LOW3.6 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW3.54 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010022 | LOW3.53 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4438 | LOW3.4 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | LOW3.4 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW3.31 | perl-base 5.40.1-6 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-34181 | LOW3.21 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42768 | LOW3.21 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5958 | LOW3.21 | sed 4.9-2 fixed in 4.9-2+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc-bin 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010023 | LOW3.17 | libc6 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45446 | LOW3.15 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.15 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW3.11 | bsdutils 1:2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56391 | LOW3.11 | coreutils 9.7-3 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | mount 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2025-14104 | LOW3.11 | util-linux 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-42769 | LOW3.01 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42770 | LOW3.01 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-9076 | LOW3.01 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-8376 | LOW3 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34180 | LOW3 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-6357 | LOW2.96 | pip 26.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45447 | LOW2.92 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-7383 | LOW2.8 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-5704 | LOW2.8 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW2.8 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-8643 | LOW2.8 | pip 26.0.1 fixed in 26.1.2 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2025-70873 | LOW2.8 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2013-4392 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW2.8 | libudev1 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | LOW2.78 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-13221 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42496 | LOW2.78 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc-bin 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc-bin 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2018-20796 | LOW2.7 | libc6 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Post-Exploit |
| CVE-2019-9192 | LOW2.7 | libc6 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14456 | LOW2.7 | libssl3t64 3.5.5-1~deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14456 | LOW2.7 | openssl 3.5.5-1~deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-14456 | LOW2.7 | openssl-provider-legacy 3.5.5-1~deb13u2 No fix yet | — | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-53910 | LOW2.7 | diffutils 1:3.10-4 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-42766 | LOW2.7 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-42767 | LOW2.7 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-12087 | LOW2.7 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-13595 | LOW2.7 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-3184 | LOW2.7 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
| CVE-2026-57432 | LOW2.57 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-48959 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-48961 | LOW2.55 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-3219 | LOW2.55 | pip 26.0.1 fixed in 26.1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2007-5686 | LOW2.5 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2017-18018 | LOW2.4 | coreutils 9.7-3 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-41991 | LOW2.4 | gzip 1.13-1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-27456 | LOW2.4 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.39 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-29111 | LOW2.39 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-41992 | LOW2.29 | gzip 1.13-1 No fix yet | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2025-5278 | LOW2.24 | coreutils 9.7-3 No fix yet | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2026-56392 | LOW2.24 | coreutils 9.7-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-45446 | LOW1.89 | openssl 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 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-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2025-69720 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-69720 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-14104 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2022-0563 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-13595 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-3184 | NONE0 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2007-5686 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-modules-bin 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam-runtime 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-54411 | NONE0 | libpam0g 1.7.0-5 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| CVE-2026-27456 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Not Applicable |
| CVE-2024-56433 | NONE0 | login.defs 1:4.17.4-2 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libncursesw6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2025-6141 | NONE0 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| TEMP-0841856-B18BAF | NONE0 | bash 5.2.37-2+b8 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-11822 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-11824 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-50812 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-50813 | NONE0 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.1% Theoretical Threat | Not Applicable |
| CVE-2026-15059 | NONE0 | libsystemd0 257.9-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-16742 | NONE0 | libsystemd0 257.9-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-15059 | NONE0 | libudev1 257.9-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-16742 | NONE0 | libudev1 257.9-1~deb13u1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53615 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | login.defs 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| TEMP-0628843-DBAD28 | NONE0 | passwd 1:4.17.4-2 No fix yet | — | Not Applicable |
| CVE-2026-57433 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.4% Theoretical Threat | Not Applicable |
| CVE-2026-7010 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Not Applicable |
| CVE-2026-15534 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-19487 | NONE0 | perl-base 5.40.1-6 No fix yet | — | Not Applicable |
| CVE-2026-7017 | NONE0 | perl-base 5.40.1-6 No fix yet | 0.3% Theoretical Threat | Not Applicable |
| TEMP-0517018-A83CE6 | NONE0 | sysvinit-utils 3.14-4 No fix yet | — | Not Applicable |
| TEMP-0290435-0B57B5 | NONE0 | tar 1.35+dfsg-3.1 No fix yet | — | Not Applicable |
| CVE-2026-53615 | NONE0 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53612 | NONE0 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53613 | NONE0 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
| CVE-2026-53614 | NONE0 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | — | Not Applicable |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.