Last scanned:
This image is safe for production use. While there are 8 exposed and 30 post-exploit vulnerabilities, all are low severity (max CVSS 5.95) and none are high or critical. The image is officially maintained and pinned by digest, reducing supply chain risk.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.4-r2 fixed in 1.2.4-r3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26519 | MEDIUM5.95 | musl-utils 1.2.4-r1 fixed in 1.2.4-r3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.1.3-r0 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.1.3-r0 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.1.3-r0 fixed in 3.1.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.1.3-r0 fixed in 3.1.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.1.3-r0 fixed in 3.1.7-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.1.3-r0 fixed in 3.1.7-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | LOW3.51 | libcrypto3 3.1.3-r0 fixed in 3.1.7-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libssl3 3.1.3-r0 fixed in 3.1.7-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.36.1-r2 fixed in 1.36.1-r6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox-binsh 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox-binsh 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox-binsh 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox-binsh 1.36.1-r2 fixed in 1.36.1-r6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | ssl_client 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | ssl_client 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | ssl_client 1.36.1-r2 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.36.1-r2 fixed in 1.36.1-r6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libcrypto3 3.1.3-r0 fixed in 3.1.4-r0 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libssl3 3.1.3-r0 fixed in 3.1.4-r0 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libcrypto3 3.1.3-r0 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libssl3 3.1.3-r0 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW2.12 | libcrypto3 3.1.3-r0 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW2.12 | libcrypto3 3.1.3-r0 fixed in 3.1.6-r0 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW2.12 | libssl3 3.1.3-r0 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW2.12 | libssl3 3.1.3-r0 fixed in 3.1.6-r0 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | libcrypto3 3.1.3-r0 fixed in 3.1.6-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | libssl3 3.1.3-r0 fixed in 3.1.6-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW1.91 | libcrypto3 3.1.3-r0 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW1.91 | libcrypto3 3.1.3-r0 fixed in 3.1.5-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW1.91 | libssl3 3.1.3-r0 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4603 | LOW1.91 | libssl3 3.1.3-r0 fixed in 3.1.5-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2511 | LOW1.73 | libcrypto3 3.1.3-r0 fixed in 3.1.4-r6 | 54.0% Actively Exploited | Post-Exploit |
| CVE-2024-2511 | LOW1.73 | libssl3 3.1.3-r0 fixed in 3.1.4-r6 | 54.0% Actively Exploited | 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.