Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker could exploit CVE-2023-44487 to launch a denial-of-service attack via rapid HTTP/2 stream resets, potentially exhausting server resources. Disabling HTTP/2 (e.g., not loading mod_http2) would fully mitigate this vulnerability. Note: CVE-2023-44487 only applies if HTTP/2 is enabled; however, the presence of other high-severity vulnerabilities (e.g., CVE-2025-69421) further elevates risk.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2023-44487 | HIGH7.8 | nghttp2-libs 1.51.0-r0 fixed in 1.51.0-r2 | 100.0% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2023-6129 | MEDIUM6.5 | libssl3 3.0.8-r0 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69421 | MEDIUM6.38 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2025-69419 | MEDIUM6.29 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2023-35945 | MEDIUM6 | nghttp2-libs 1.51.0-r0 fixed in 1.51.0-r1 | 1.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
| CVE-2025-26519 | MEDIUM5.95 | musl 1.2.3-r4 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2025-26519 | MEDIUM5.95 | musl-utils 1.2.3-r4 fixed in 1.2.3-r6 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libcrypto3 3.0.8-r0 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2024-50602 | MEDIUM5.9 | libexpat 2.5.0-r0 fixed in 2.6.4-r0 | 1.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-6237 | MEDIUM5.9 | libssl3 3.0.8-r0 fixed in 3.0.12-r3 | 2.3% Low-Moderate Risk | Directly Exposed |
| CVE-2024-5535 | MEDIUM5.9 | libssl3 3.0.8-r0 fixed in 3.0.14-r0 | 5.6% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libcrypto3 3.0.8-r0 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9230 | MEDIUM5.6 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4741 | MEDIUM5.6 | libssl3 3.0.8-r0 fixed in 3.0.14-r0 | 2.9% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2024-0727 | MEDIUM5.5 | libssl3 3.0.8-r0 fixed in 3.0.12-r4 | 3.2% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.9-r3 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.10-r0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libcrypto3 3.0.8-r0 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0465 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.8-r2 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-0466 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.8-r3 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3446 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.9-r3 | 5.5% Low-Moderate Risk | Directly Exposed |
| CVE-2023-3817 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.10-r0 | 2.6% Low-Moderate Risk | Directly Exposed |
| CVE-2023-5678 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.12-r1 | 4.5% Low-Moderate Risk | Directly Exposed |
| CVE-2024-4603 | MEDIUM5.3 | libssl3 3.0.8-r0 fixed in 3.0.13-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-1255 | MEDIUM5.02 | libssl3 3.0.8-r0 fixed in 3.0.8-r4 | 1.0% Theoretical Threat | Directly Exposed |
| CVE-2025-69420 | MEDIUM5.02 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.8% Theoretical Threat | Directly Exposed |
| CVE-2026-22796 | MEDIUM5.02 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2024-2511 | MEDIUM4.81 | libssl3 3.0.8-r0 fixed in 3.0.12-r5 | 54.0% Actively Exploited | Directly Exposed |
| CVE-2023-49582 | MEDIUM4.67 | apr 1.7.2-r0 fixed in 1.7.5-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-52426 | MEDIUM4.67 | libexpat 2.5.0-r0 fixed in 2.6.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-22795 | MEDIUM4.67 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-38545 | MEDIUM4.58 | libcurl 7.87.0-r1 fixed in 8.4.0-r0 | 78.5% Actively Exploited | Post-Exploit |
| CVE-2023-2975 | MEDIUM4.5 | libcrypto3 3.0.8-r0 fixed in 3.0.9-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2023-2975 | MEDIUM4.5 | libssl3 3.0.8-r0 fixed in 3.0.9-r2 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2025-15467 | MEDIUM4.06 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2025-15467 | MEDIUM4.06 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 47.6% High Exploitation Risk | Post-Exploit |
| CVE-2024-13176 | MEDIUM4 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2024-13176 | MEDIUM4 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2025-68160 | MEDIUM4 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2023-47038 | LOW3.98 | perl 5.36.0-r0 fixed in 5.36.2-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2024-9143 | LOW3.7 | libcrypto3 3.0.8-r0 fixed in 3.0.15-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2024-9143 | LOW3.7 | libssl3 3.0.8-r0 fixed in 3.0.15-r1 | 6.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-27535 | LOW3.54 | libcurl 7.87.0-r1 fixed in 7.88.1-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27536 | LOW3.54 | libcurl 7.87.0-r1 fixed in 7.88.1-r1 | 1.6% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27537 | LOW3.54 | libcurl 7.87.0-r1 fixed in 7.88.1-r1 | 1.9% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28320 | LOW3.54 | libcurl 7.87.0-r1 fixed in 8.1.0-r0 | 2.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28321 | LOW3.54 | libcurl 7.87.0-r1 fixed in 8.1.0-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-45491 | LOW3.53 | libexpat 2.5.0-r0 fixed in 2.6.3-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-45492 | LOW3.53 | libexpat 2.5.0-r0 fixed in 2.6.3-r0 | 1.4% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libcrypto3 3.0.8-r0 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2023-38039 | LOW3.51 | libcurl 7.87.0-r1 fixed in 8.3.0-r0 | 62.2% Actively Exploited | Post-Exploit |
| CVE-2024-6119 | LOW3.51 | libssl3 3.0.8-r0 fixed in 3.0.15-r0 | 66.6% Actively Exploited | Post-Exploit |
| CVE-2025-69418 | LOW3.4 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2025-69418 | LOW3.4 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 0.1% Theoretical Threat | Directly Exposed |
| CVE-2023-23915 | LOW3.31 | libcurl 7.87.0-r1 fixed in 7.87.0-r2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-27538 | LOW3.3 | libcurl 7.87.0-r1 fixed in 7.88.1-r1 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2379 | LOW3.24 | libcurl 7.87.0-r1 fixed in 8.7.1-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46219 | LOW3.18 | libcurl 7.87.0-r1 fixed in 8.5.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-0853 | LOW3.18 | libcurl 7.87.0-r1 fixed in 8.6.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2466 | LOW3.18 | libcurl 7.87.0-r1 fixed in 8.7.1-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2004 | LOW3.18 | libcurl 7.87.0-r1 fixed in 8.7.1-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27533 | LOW3.17 | libcurl 7.87.0-r1 fixed in 7.88.1-r1 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-27534 | LOW3.17 | libcurl 7.87.0-r1 fixed in 7.88.1-r1 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-2398 | LOW3.1 | libcurl 7.87.0-r1 fixed in 8.7.1-r0 | 36.1% High Exploitation Risk | Post-Exploit |
| CVE-2025-9232 | LOW3.1 | libcrypto3 3.0.8-r0 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2025-9232 | LOW3.1 | libssl3 3.0.8-r0 fixed in 3.0.19-r0 | 2.0% Low-Moderate Risk | Directly Exposed |
| CVE-2023-2650 | LOW3.04 | libcrypto3 3.0.8-r0 fixed in 3.0.9-r0 | 73.5% Actively Exploited | Post-Exploit |
| CVE-2023-2650 | LOW3.04 | libssl3 3.0.8-r0 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-23914 | LOW2.78 | libcurl 7.87.0-r1 fixed in 7.87.0-r2 | 0.9% Theoretical Threat | Post-Exploit |
| CVE-2023-0464 | LOW2.7 | libcrypto3 3.0.8-r0 fixed in 3.0.8-r1 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r0 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28319 | LOW2.7 | libcurl 7.87.0-r1 fixed in 8.1.0-r0 | 2.5% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6197 | LOW2.7 | libcurl 7.87.0-r1 fixed in 8.9.0-r0 | 4.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-52425 | LOW2.7 | libexpat 2.5.0-r0 fixed in 2.6.0-r0 | 1.8% Low-Moderate Risk | Post-Exploit |
| CVE-2024-28757 | LOW2.7 | libexpat 2.5.0-r0 fixed in 2.6.2-r0 | 2.0% Low-Moderate Risk | Post-Exploit |
| CVE-2024-45490 | LOW2.7 | libexpat 2.5.0-r0 fixed in 2.6.3-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-0464 | LOW2.7 | libssl3 3.0.8-r0 fixed in 3.0.8-r1 | 3.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-5363 | LOW2.7 | libssl3 3.0.8-r0 fixed in 3.0.12-r0 | 3.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-6129 | LOW2.34 | libcrypto3 3.0.8-r0 fixed in 3.0.12-r2 | 2.3% Low-Moderate Risk | Post-Exploit |
| CVE-2023-23916 | LOW2.34 | libcurl 7.87.0-r1 fixed in 7.87.0-r2 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-46218 | LOW2.34 | libcurl 7.87.0-r1 fixed in 8.5.0-r0 | 1.7% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28484 | LOW2.34 | libxml2 2.10.3-r1 fixed in 2.10.4-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2023-29469 | LOW2.34 | libxml2 2.10.3-r1 fixed in 2.10.4-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2023-28322 | LOW2.22 | libcurl 7.87.0-r1 fixed in 8.1.0-r0 | 2.2% Low-Moderate Risk | Post-Exploit |
| CVE-2023-38546 | LOW2.22 | libcurl 7.87.0-r1 fixed in 8.4.0-r0 | 6.2% Low-Moderate Risk | Post-Exploit |
| CVE-2024-6874 | LOW2.19 | libcurl 7.87.0-r1 fixed in 8.9.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.