Last scanned:
This image is safe for production use. While the image contains 11 exposed and 37 post-exploit vulnerabilities, all are low severity (max CVSS 5.95 and 3.98 respectively) and pose negligible practical risk, especially given the image's trusted source and immutability. No actionable exploits are present, and the default configuration minimizes attack surface.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.4_git20230717-r4 fixed in 1.2.4_git20230717-r5 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.1.4-r2 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.1.4-r2 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-6042 | MEDIUM4.67 | musl 1.2.4_git20230717-r4 fixed in 1.2.4_git20230717-r6 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.1.4-r2 fixed in 3.1.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.1.4-r2 fixed in 3.1.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | LOW3.98 | musl 1.2.4_git20230717-r4 fixed in 1.2.4_git20230717-r6 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-40200 | LOW3.98 | musl-utils 1.2.4_git20230717-r4 fixed in 1.2.4_git20230717-r6 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.1.4-r2 fixed in 3.1.7-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.1.4-r2 fixed in 3.1.7-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-26519 | LOW3.57 | musl-utils 1.2.4_git20230717-r4 fixed in 1.2.4_git20230717-r5 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libcrypto3 3.1.4-r2 fixed in 3.1.7-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libssl3 3.1.4-r2 fixed in 3.1.7-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libcrypto3 3.1.4-r2 fixed in 3.1.8-r1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl3 3.1.4-r2 fixed in 3.1.8-r1 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-42363 | LOW2.8 | busybox 1.36.1-r15 fixed in 1.36.1-r17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox 1.36.1-r15 fixed in 1.36.1-r19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox 1.36.1-r15 fixed in 1.36.1-r19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.36.1-r15 fixed in 1.36.1-r16 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox-binsh 1.36.1-r15 fixed in 1.36.1-r17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox-binsh 1.36.1-r15 fixed in 1.36.1-r19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox-binsh 1.36.1-r15 fixed in 1.36.1-r19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox-binsh 1.36.1-r15 fixed in 1.36.1-r16 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-6042 | LOW2.8 | musl-utils 1.2.4_git20230717-r4 fixed in 1.2.4_git20230717-r6 | 0.2% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | ssl_client 1.36.1-r15 fixed in 1.36.1-r17 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | ssl_client 1.36.1-r15 fixed in 1.36.1-r19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | ssl_client 1.36.1-r15 fixed in 1.36.1-r19 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.36.1-r15 fixed in 1.36.1-r16 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libcrypto3 3.1.4-r2 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libssl3 3.1.4-r2 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW2.12 | libcrypto3 3.1.4-r2 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW2.12 | libcrypto3 3.1.4-r2 fixed in 3.1.6-r0 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW2.12 | libssl3 3.1.4-r2 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW2.12 | libssl3 3.1.4-r2 fixed in 3.1.6-r0 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9230 | LOW2.02 | libcrypto3 3.1.4-r2 fixed in 3.1.8-r1 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | libcrypto3 3.1.4-r2 fixed in 3.1.6-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2025-9230 | LOW2.02 | libssl3 3.1.4-r2 fixed in 3.1.8-r1 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | libssl3 3.1.4-r2 fixed in 3.1.6-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW1.91 | libcrypto3 3.1.4-r2 fixed in 3.1.5-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW1.91 | libssl3 3.1.4-r2 fixed in 3.1.5-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW1.73 | libcrypto3 3.1.4-r2 fixed in 3.1.4-r6 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2024-2511 | LOW1.73 | libssl3 3.1.4-r2 fixed in 3.1.4-r6 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox 1.36.1-r15 fixed in 1.36.1-r21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | busybox-binsh 1.36.1-r15 fixed in 1.36.1-r21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2025-46394 | LOW1.68 | ssl_client 1.36.1-r15 fixed in 1.36.1-r21 | 0.1% Theoretical Threat | Post-Exploit |
| CVE-2024-58251 | NONE0 | busybox 1.36.1-r15 fixed in 1.36.1-r21 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58251 | NONE0 | busybox-binsh 1.36.1-r15 fixed in 1.36.1-r21 | 0.2% Theoretical Threat | Not Applicable |
| CVE-2024-58251 | NONE0 | ssl_client 1.36.1-r15 fixed in 1.36.1-r21 | 0.2% Theoretical Threat | 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.