Last scanned:
This image is safe for production use. Although the scan detected 21 exposed and 16 post-exploit vulnerabilities, all are low severity with maximum scores of 5.35 and 3.53 respectively. No critical or high-severity findings were listed in the top findings, and the image is pinned by digest from a reputable source, supporting its safe deployment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-34181 | MEDIUM5.35 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-42768 | MEDIUM5.35 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% 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~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-42770 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-9076 | MEDIUM5.02 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-31789 | MEDIUM5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-34180 | MEDIUM5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2026-7383 | MEDIUM4.67 | libssl3t64 3.5.5-1~deb13u1 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-28388 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.1% Low-Moderate Risk | 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-42766 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2026-42767 | MEDIUM4.5 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% 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-28387 | MEDIUM4.13 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2010-4756 | MEDIUM4 | libc6 2.41-12+deb13u2 No fix yet | 2.6% Low-Moderate Risk | Directly Exposed |
| 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 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-2673 | LOW3.31 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| 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~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-45447 | LOW2.92 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 5.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-45445 | LOW2.78 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.6% Theoretical Threat | 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-28389 | LOW2.7 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-28390 | LOW2.7 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34183 | LOW2.7 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-34182 | LOW2.26 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-31790 | LOW2.12 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.5-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-42764 | LOW2.12 | libssl3t64 3.5.5-1~deb13u1 fixed in 3.5.6-1~deb13u2 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-4437 | LOW1.99 | libc6 2.41-12+deb13u2 fixed in 2.41-12+deb13u3 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-6238 | LOW1.99 | libc6 2.41-12+deb13u2 No fix yet | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2019-1010024 | LOW1.91 | libc6 2.41-12+deb13u2 No fix yet | 3.2% Low-Moderate Risk | Post-Exploit |
| CVE-2019-1010025 | LOW1.91 | libc6 2.41-12+deb13u2 No fix yet | 2.3% Low-Moderate Risk | 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.
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.