Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. An attacker exploiting CVE-2023-5363 could potentially decrypt sensitive network traffic if TLS is enabled and affected cipher modes are used. Note that CVE-2023-6129 only impacts PowerPC CPU architectures, which may not be relevant for typical x86 deployments. Post-exploit vulnerabilities are not exploitable in default memcached operation, but the number of exposed vulnerabilities demands careful consideration.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-5363 | HIGH7.5 | libcrypto3 3.0.7-r2 fixed in 3.0.12-r0 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | HIGH7.5 | libssl3 3.0.7-r2 fixed in 3.0.12-r0 | 3.3% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2022-4304 | MEDIUM6.79 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 16.2% High Exploitation Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libcrypto3 3.0.7-r2 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | MEDIUM6.5 | libssl3 3.0.7-r2 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.3-r4 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libcrypto3 3.0.7-r2 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libcrypto3 3.0.7-r2 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.7-r2 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.7-r2 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libcrypto3 3.0.7-r2 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.7-r2 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.0.7-r2 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.7-r2 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libcrypto3 3.0.7-r2 fixed in 3.0.9-r3 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libcrypto3 3.0.7-r2 fixed in 3.0.10-r0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto3 3.0.7-r2 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libcrypto3 3.0.7-r2 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl3 3.0.7-r2 fixed in 3.0.8-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl3 3.0.7-r2 fixed in 3.0.8-r3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl3 3.0.7-r2 fixed in 3.0.9-r3 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl3 3.0.7-r2 fixed in 3.0.10-r0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.7-r2 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.7-r2 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libssl3 3.0.7-r2 fixed in 3.0.8-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2022-4203 | MEDIUM4.9 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2022-4203 | MEDIUM4.9 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 1.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libcrypto3 3.0.7-r2 fixed in 3.0.12-r5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.7-r2 fixed in 3.0.12-r5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libcrypto3 3.0.7-r2 fixed in 3.0.9-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.0.7-r2 fixed in 3.0.9-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.0.7-r2 fixed in 3.0.15-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.7-r2 fixed in 3.0.15-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | LOW3.51 | libcrypto3 3.0.7-r2 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libssl3 3.0.7-r2 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2023-0286 | LOW3.46 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 59.5% Actively Exploited | Post-Exploit |
| CVE-2023-0286 | LOW3.46 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 59.5% Actively Exploited | Post-Exploit |
| CVE-2025-69418 | LOW3.4 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2022-4450 | LOW3.1 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2022-4450 | LOW3.1 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 20.4% High Exploitation Risk | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libcrypto3 3.0.7-r2 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.7-r2 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2650 | LOW3.04 | libcrypto3 3.0.7-r2 fixed in 3.0.9-r0 | 73.5% Actively Exploited | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | libssl3 3.0.7-r2 fixed in 3.0.9-r0 | 73.5% Actively Exploited | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox 1.35.0-r29 fixed in 1.35.0-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | busybox-binsh 1.35.0-r29 fixed in 1.35.0-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42363 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42364 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42365 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r31 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-42366 | LOW2.8 | ssl_client 1.35.0-r29 fixed in 1.35.0-r30 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0216 | LOW2.7 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0217 | LOW2.7 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0401 | LOW2.7 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | LOW2.7 | libcrypto3 3.0.7-r2 fixed in 3.0.8-r1 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0215 | LOW2.7 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 4.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0216 | LOW2.7 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0217 | LOW2.7 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0401 | LOW2.7 | libssl3 3.0.7-r2 fixed in 3.0.8-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | LOW2.7 | libssl3 3.0.7-r2 fixed in 3.0.8-r1 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2025-26519 | NONE0 | musl-utils 1.2.3-r4 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Not Applicable |
Want to check another image? Run a full scan with the Docker Security Scanner.