Last scanned:
This image is safe for production use. While 13 exposed and 35 post-exploit vulnerabilities exist, they are all low severity (max CVSS 5.95) and do not pose significant risk. The image is from Docker Official, pinned by digest, ensuring authenticity and immutability.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.4-r0 fixed in 1.2.4-r3 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.1.0-r4 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.1.0-r4 fixed in 3.1.4-r5 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libcrypto3 3.1.0-r4 fixed in 3.1.5-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.1.0-r4 fixed in 3.1.5-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libcrypto3 3.1.0-r4 fixed in 3.1.4-r6 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.1.0-r4 fixed in 3.1.4-r6 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libcrypto3 3.1.0-r4 fixed in 3.1.1-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.1.0-r4 fixed in 3.1.1-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.1.0-r4 fixed in 3.1.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.1.0-r4 fixed in 3.1.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.1.0-r4 fixed in 3.1.7-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.1.0-r4 fixed in 3.1.7-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2022-48174 | LOW3.53 | busybox 1.36.0-r9 fixed in 1.36.1-r1 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48174 | LOW3.53 | busybox-binsh 1.36.0-r9 fixed in 1.36.1-r1 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2022-48174 | LOW3.53 | ssl_client 1.36.0-r9 fixed in 1.36.1-r1 | 3.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libcrypto3 3.1.0-r4 fixed in 3.1.7-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libssl3 3.1.0-r4 fixed in 3.1.7-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | libcrypto3 3.1.0-r4 fixed in 3.1.1-r0 | 73.5% Actively Exploited | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | libssl3 3.1.0-r4 fixed in 3.1.1-r0 | 73.5% Actively Exploited | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.36.0-r9 fixed in 1.36.1-r6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox-binsh 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox-binsh 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox-binsh 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox-binsh 1.36.0-r9 fixed in 1.36.1-r6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | ssl_client 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | ssl_client 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | ssl_client 1.36.0-r9 fixed in 1.36.1-r7 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.36.0-r9 fixed in 1.36.1-r6 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libcrypto3 3.1.0-r4 fixed in 3.1.4-r0 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libssl3 3.1.0-r4 fixed in 3.1.4-r0 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libcrypto3 3.1.0-r4 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libssl3 3.1.0-r4 fixed in 3.1.4-r3 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW2.12 | libcrypto3 3.1.0-r4 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW2.12 | libcrypto3 3.1.0-r4 fixed in 3.1.6-r0 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6237 | LOW2.12 | libssl3 3.1.0-r4 fixed in 3.1.4-r4 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-5535 | LOW2.12 | libssl3 3.1.0-r4 fixed in 3.1.6-r0 | 5.6% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | libcrypto3 3.1.0-r4 fixed in 3.1.6-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-4741 | LOW2.02 | libssl3 3.1.0-r4 fixed in 3.1.6-r0 | 2.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW1.91 | libcrypto3 3.1.0-r4 fixed in 3.1.1-r3 | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW1.91 | libcrypto3 3.1.0-r4 fixed in 3.1.2-r0 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW1.91 | libcrypto3 3.1.0-r4 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3446 | LOW1.91 | libssl3 3.1.0-r4 fixed in 3.1.1-r3 | 5.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-3817 | LOW1.91 | libssl3 3.1.0-r4 fixed in 3.1.2-r0 | 2.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5678 | LOW1.91 | libssl3 3.1.0-r4 fixed in 3.1.4-r1 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2025-26519 | NONE0 | musl-utils 1.2.4-r0 fixed in 1.2.4-r3 | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.