Last scanned:
This image carries significant risk; production deployment is highly discouraged without strict compensating controls. If the libwebp flaw is reached through an image-processing path, an attacker could execute code inside the container, and if HTTP/2 or a vulnerable nginx rewrite rule is enabled, an attacker could exhaust resources or crash workers. Note: CVE-2023-44487 only applies if an HTTP/2 listener is enabled, and CVE-2026-42945 only applies if a vulnerable rewrite rule is configured. Keeping HTTP/2 disabled removes the exposure to CVE-2023-44487 in this setup, and rebuilding the image without the WebP library would fully eliminate CVE-2023-4863. Before production use, confirm these features are off and plan an upgrade off the end-of-support base image.
Hardening plan for this image · 5 steps. The first closes 2 actively exploited CVEs.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-4863 | HIGH8 | libwebp 1.2.4-r2 fixed in 1.2.4-r3 | 100.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-42945 | HIGH8 | nginx 1.25.1 No fix yet | 68.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-44487 | HIGH7.8 | nghttp2-libs 1.51.0-r1 fixed in 1.51.0-r2 | 100.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-9256 | HIGH7.45 | nginx 1.25.1 No fix yet | 10.9% High Exploitation Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-15467 | MEDIUM6 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2025-15467 | MEDIUM6 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 74.8% Actively Exploited | Directly Exposed |
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.3-r5 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26519 | MEDIUM5.95 | musl-utils 1.2.3-r5 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libcrypto3 3.0.10-r0 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libcrypto3 3.0.10-r0 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.10-r0 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.10-r0 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.9 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.9 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-1642 | MEDIUM5.9 | nginx 1.25.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-45491 | MEDIUM5.88 | libexpat 2.5.0-r0 fixed in 2.6.3-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45492 | MEDIUM5.88 | libexpat 2.5.0-r0 fixed in 2.6.3-r0 | 1.4% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6119 | MEDIUM5.85 | libcrypto3 3.0.10-r0 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2024-6119 | MEDIUM5.85 | libssl3 3.0.10-r0 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Directly Exposed |
| CVE-2026-27654 | MEDIUM5.66 | nginx 1.25.1 No fix yet | 25.9% High Exploitation Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libcrypto3 3.0.10-r0 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.10-r0 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-32760 | MEDIUM5.52 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.0.10-r0 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.10-r0 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-22795 | MEDIUM5.5 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto3 3.0.10-r0 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libcrypto3 3.0.10-r0 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.10-r0 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.10-r0 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-42055 | MEDIUM4.86 | nginx 1.25.1 No fix yet | 6.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libcrypto3 3.0.10-r0 fixed in 3.0.12-r5 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.10-r0 fixed in 3.0.12-r5 | 52.4% Actively Exploited | Directly Exposed |
| CVE-2026-40701 | MEDIUM4.8 | nginx 1.25.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-42934 | MEDIUM4.8 | nginx 1.25.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-48142 | MEDIUM4.8 | nginx 1.25.1 No fix yet | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4.7 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-27784 | MEDIUM4.68 | nginx 1.25.1 No fix yet | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-32647 | MEDIUM4.68 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-38545 | MEDIUM4.58 | curl 8.2.1-r0 fixed in 8.4.0-r0 | 78.7% Actively Exploited | Post-Exploit |
| CVE-2023-38545 | MEDIUM4.58 | libcurl 8.2.1-r0 fixed in 8.4.0-r0 | 78.7% Actively Exploited | Post-Exploit |
| CVE-2023-5363 | MEDIUM4.5 | libcrypto3 3.0.10-r0 fixed in 3.0.12-r0 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2023-52425 | MEDIUM4.5 | libexpat 2.5.0-r0 fixed in 2.6.0-r0 | 2.1% Low-Moderate Risk | Directly Exposed |
| CVE-2024-28757 | MEDIUM4.5 | libexpat 2.5.0-r0 fixed in 2.6.2-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-45490 | MEDIUM4.5 | libexpat 2.5.0-r0 fixed in 2.6.3-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5363 | MEDIUM4.5 | libssl3 3.0.10-r0 fixed in 3.0.12-r0 | 3.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM4.5 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-27651 | MEDIUM4.5 | nginx 1.25.1 No fix yet | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2024-34161 | MEDIUM4.5 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-35200 | MEDIUM4.5 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM4.44 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-42946 | MEDIUM4.44 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2025-23419 | MEDIUM4.3 | nginx 1.25.1 No fix yet | 2.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-31079 | MEDIUM4.08 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | MEDIUM4 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2024-7347 | MEDIUM4 | nginx 1.25.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-43787 | LOW3.98 | libx11 1.8.4-r1 fixed in 1.8.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-6129 | LOW3.9 | libcrypto3 3.0.10-r0 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6129 | LOW3.9 | libssl3 3.0.10-r0 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2026-40460 | LOW3.9 | nginx 1.25.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-24990 | LOW3.83 | nginx 1.25.1 No fix yet | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.0.10-r0 fixed in 3.0.15-r1 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.10-r0 fixed in 3.0.15-r1 | 5.8% Low-Moderate Risk | Directly Exposed |
| CVE-2026-28753 | LOW3.7 | nginx 1.25.1 No fix yet | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2024-50602 | LOW3.54 | libexpat 2.5.0-r0 fixed in 2.6.4-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38039 | LOW3.51 | curl 8.2.1-r0 fixed in 8.3.0-r0 | 56.4% Actively Exploited | Post-Exploit |
| CVE-2023-38039 | LOW3.51 | libcurl 8.2.1-r0 fixed in 8.3.0-r0 | 56.4% Actively Exploited | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | curl 8.2.1-r0 fixed in 8.7.1-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-2004 | LOW3.18 | libcurl 8.2.1-r0 fixed in 8.7.1-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2025-53859 | LOW3.15 | nginx 1.25.1 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2024-2398 | LOW3.1 | curl 8.2.1-r0 fixed in 8.7.1-r0 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl 8.2.1-r0 fixed in 8.7.1-r0 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libcrypto3 3.0.10-r0 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.10-r0 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| 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-52426 | LOW2.8 | libexpat 2.5.0-r0 fixed in 2.6.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-43785 | LOW2.8 | libx11 1.8.4-r1 fixed in 1.8.7-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2023-43786 | LOW2.8 | libx11 1.8.4-r1 fixed in 1.8.7-r0 | 0.5% Theoretical Threat | Directly Exposed |
| 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-2024-6197 | LOW2.7 | curl 8.2.1-r0 fixed in 8.9.0-r0 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6197 | LOW2.7 | libcurl 8.2.1-r0 fixed in 8.9.0-r0 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW2.34 | curl 8.2.1-r0 fixed in 8.5.0-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW2.34 | libcurl 8.2.1-r0 fixed in 8.5.0-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | curl 8.2.1-r0 fixed in 8.4.0-r0 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-38546 | LOW2.22 | libcurl 8.2.1-r0 fixed in 8.4.0-r0 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-6874 | LOW2.19 | curl 8.2.1-r0 fixed in 8.9.0-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-6874 | LOW2.19 | libcurl 8.2.1-r0 fixed in 8.9.0-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2024-2379 | LOW1.94 | curl 8.2.1-r0 fixed in 8.7.1-r0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW1.94 | libcurl 8.2.1-r0 fixed in 8.7.1-r0 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW1.91 | curl 8.2.1-r0 fixed in 8.5.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0853 | LOW1.91 | curl 8.2.1-r0 fixed in 8.6.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2466 | LOW1.91 | curl 8.2.1-r0 fixed in 8.7.1-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW1.91 | libcurl 8.2.1-r0 fixed in 8.5.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0853 | LOW1.91 | libcurl 8.2.1-r0 fixed in 8.6.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2466 | LOW1.91 | libcurl 8.2.1-r0 fixed in 8.7.1-r0 | 1.5% Low-Moderate Risk | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.