Last scanned:
··This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The most significant findings, CVE-2026-86145 in the PCRE2 library and CVE-2026-11822 in the SQLite library, could lead to code execution, but each only becomes relevant when an application in the container feeds it untrusted regular expressions or attacker-supplied databases. Under normal Bun runtime operation these paths are not expected to be exercised, so the practical risk is conditional on how the workload is built and used. Because the container runs as root by default, any successful exploit would carry more weight, so running it as a non-root user and reviewing whether these libraries are needed would reduce exposure.
Hardening plan for this image · 5 steps
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-86145 | MEDIUM6.56 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11822 | MEDIUM6.24 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-11824 | MEDIUM6.24 | libsqlite3-0 3.46.1-7+deb13u1 fixed in 3.46.1-7+deb13u2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-103111 | MEDIUM6.08 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89157 | MEDIUM5.92 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-5435 | MEDIUM5.9 | libc-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5435 | MEDIUM5.9 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6791 | MEDIUM5.9 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-77117 | MEDIUM5.9 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80489 | MEDIUM5.9 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | 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-54872 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-72897 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75805 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-77696 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | 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-54872 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-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.5-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.5-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.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42769 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.9 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc-bin 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-6368 | MEDIUM5.5 | libc6 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-15059 | MEDIUM5.5 | libudev1 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7383 | MEDIUM5.5 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.8% 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-45445 | MEDIUM5.46 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45445 | MEDIUM5.46 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc-bin 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4046 | MEDIUM5.3 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-8674 | MEDIUM5.3 | libc6 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-54873 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-75804 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-75806 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84784 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42772 | MEDIUM5.3 | openssl-provider-legacy 3.5.5-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.5-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.5-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.5-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.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42766 | MEDIUM5.3 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42767 | MEDIUM5.3 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libsystemd0 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-16742 | MEDIUM5.28 | libudev1 257.9-1~deb13u1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4437 | MEDIUM5.2 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-4437 | MEDIUM5.2 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89158 | MEDIUM5.2 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-89160 | MEDIUM5.2 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 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+deb13u2 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u4 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-5450 | MEDIUM5 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u4 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-5928 | MEDIUM5 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u4 | 0.4% 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-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+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-18374 | MEDIUM4.9 | libc6 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-45447 | MEDIUM4.86 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 4.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53615 | MEDIUM4.8 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78408 | MEDIUM4.74 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89156 | MEDIUM4.72 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54875 | MEDIUM4.7 | libssl3t64 3.5.5-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.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89161 | MEDIUM4.68 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM4.68 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-29111 | MEDIUM4.68 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-76642 | MEDIUM4.68 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-78410 | MEDIUM4.68 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | gcc-14-base 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libgcc-s1 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-95619 | MEDIUM4.62 | libstdc++6 14.2.0-19 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3t64 3.5.5-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.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-34183 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63072 | MEDIUM4.5 | openssl-provider-legacy 3.5.5-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.5-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.5-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.5-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.5-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.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42497 | MEDIUM4.5 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-57433 | MEDIUM4.5 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9538 | MEDIUM4.5 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-84782 | MEDIUM4.44 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34182 | MEDIUM4.44 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-50812 | MEDIUM4.4 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-50813 | MEDIUM4.4 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-54369 | MEDIUM4.26 | libacl1 2.3.2-2+b1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | bsdutils 1:2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | gcc-14-base 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libblkid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc-bin 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc-bin 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-86805 | MEDIUM4.2 | libc6 2.41-12+deb13u2 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-95818 | MEDIUM4.2 | libc6 2.41-12+deb13u2 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4878 | MEDIUM4.2 | libcap2 1:2.75-10+b8 fixed in 1:2.75-10+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libgcc-s1 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | liblastlog2-2 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libmount1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libsmartcols1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-102010 | MEDIUM4.2 | libstdc++6 14.2.0-19 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | libuuid1 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | mount 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53612 | MEDIUM4.2 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53613 | MEDIUM4.2 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-53614 | MEDIUM4.2 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-78409 | MEDIUM4.2 | util-linux 2.41-5 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc-bin 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19542 | MEDIUM4.2 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-89092 | MEDIUM4.2 | libc6 2.41-12+deb13u2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc-bin 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19499 | MEDIUM4.08 | libc6 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4105 | MEDIUM4.02 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc-bin 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-4438 | MEDIUM4 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-6238 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-15649 | LOW3.9 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-19487 | LOW3.9 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc-bin 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2010-4756 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2018-20796 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010022 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010023 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010024 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2019-1010025 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 2.5% Low-Moderate Risk | Directly Exposed |
| CVE-2019-9192 | LOW3.9 | libc6 2.41-12+deb13u2 No fix yet | 2.4% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libsystemd0 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40225 | LOW3.84 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40226 | LOW3.84 | libudev1 257.9-1~deb13u1 fixed in 257.13-1~deb13u1 | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54370 | LOW3.78 | libacl1 2.3.2-2+b1 No fix yet | <0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-54371 | LOW3.78 | libattr1 1:2.5.2-3 No fix yet | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.78 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | LOW3.78 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-34181 | LOW3.78 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | LOW3.78 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-5958 | LOW3.78 | sed 4.9-2 fixed in 4.9-2+deb13u1 | 0.1% Theoretical Threat | 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+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-97399 | LOW3.7 | libc6 2.41-12+deb13u2 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35189 | LOW3.7 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-35191 | LOW3.7 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | libssl3t64 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3t64 3.5.5-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.5-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.5-1~deb13u2 fixed in 3.5.7-1~deb13u3 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-45446 | LOW3.7 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | openssl-provider-legacy 3.5.5-1~deb13u2 fixed in 3.5.7-1~deb13u2 | 0.3% 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-2026-15534 | LOW3.42 | perl-base 5.40.1-6 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31437 | LOW3.31 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31438 | LOW3.31 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-31439 | LOW3.31 | libudev1 257.9-1~deb13u1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-5704 | LOW3.3 | tar 1.35+dfsg-3.1 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-40228 | LOW3.3 | libsystemd0 257.9-1~deb13u1 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-40228 | LOW3.3 | libudev1 257.9-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-13595 | LOW3.18 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-34743 | LOW3.18 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-12087 | LOW3.18 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-13595 | LOW3.18 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-3184 | LOW3.18 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2021-45346 | LOW3.12 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 1.6% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| 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-48959 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-48961 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-7010 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-7017 | LOW3 | perl-base 5.40.1-6 fixed in 5.40.1-6+deb13u1 | 0.3% Theoretical Threat | Directly Exposed |
| 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 | liblastlog2-2 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 | liblastlog2-2 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-27456 | LOW2.82 | bsdutils 1:2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-41991 | LOW2.82 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libblkid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | liblastlog2-2 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libmount1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libsmartcols1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | libuuid1 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | mount 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27456 | LOW2.82 | util-linux 2.41-5 fixed in 2.41.5-0+deb13u1 | 0.2% Theoretical Threat | Directly Exposed |
| 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 | 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-2025-69720 | LOW2.81 | libtinfo6 6.5+20250216-2 No fix yet | 0.5% 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.9-1~deb13u1 No fix yet | 0.5% 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-41992 | LOW2.7 | gzip 1.13-1 fixed in 1.13-1+deb13u1 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-18477 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | <0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-18508 | LOW2.64 | tar 1.35+dfsg-3.1 No fix yet | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2026-89162 | LOW2.64 | libpcre2-8-0 10.46-1~deb13u1 fixed in 10.46-1~deb13u2 | 0.2% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-70873 | LOW2.64 | libsqlite3-0 3.46.1-7+deb13u1 No fix yet | 0.5% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| DSA-6549-1 | LOW2.4 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| TEMP-1147318-639065 | LOW2.4 | liblzma5 5.8.1-1 fixed in 5.8.1-1+deb13u2 | — | Directly Exposed |
| CVE-2026-82560 | LOW2.4 | perl-base 5.40.1-6 No fix yet | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | bsdutils 1:2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| 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-2025-14104 | LOW2.34 | libblkid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | liblastlog2-2 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libmount1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libsmartcols1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | libuuid1 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | login 1:4.16.0-2+really2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-14104 | LOW2.34 | mount 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2005-2541 | LOW2.34 | tar 1.35+dfsg-3.1 No fix yet | 4.0% Low-Moderate Risk | Post-Exploit |
| CVE-2025-14104 | LOW2.34 | util-linux 2.41-5 fixed in 2.41.3-1 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-3374 | LOW2.22 | apt 3.0.3 No fix yet | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | bsdutils 1:2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| 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-2022-0563 | LOW1.99 | libblkid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | liblastlog2-2 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libmount1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libsmartcols1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | libuuid1 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2022-0563 | LOW1.99 | login 1:4.16.0-2+really2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | login.defs 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | mount 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2007-5686 | LOW1.99 | passwd 1:4.17.4-2 No fix yet | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2022-0563 | LOW1.99 | util-linux 2.41-5 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| 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-2025-6141 | LOW1.68 | libtinfo6 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-base 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-6141 | LOW1.68 | ncurses-bin 6.5+20250216-2 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2011-4116 | LOW1.68 | perl-base 5.40.1-6 No fix yet | 0.5% Theoretical Threat | Directly Exposed |
| TEMP-0841856-B18BAF | LOW1.5 | bash 5.2.37-2+b8 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 |
| TEMP-0290435-0B57B5 | LOW1.5 | tar 1.35+dfsg-3.1 No fix yet | — | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.