Last scanned:
This base/runtime image ships critical vulnerabilities that any image built on it would inherit; they must be remediated before the final image goes to production. Remote attackers could run code inside the PHP runtime, and because the container runs as root, that code would carry root privileges and could expose data or disrupt the service built on top. Both top PHP flaws, CVE-2026-109618 and CVE-2026-109619, are actively exploited and enabled in the default configuration, so anyone who can reach a PHP-serving port can attempt them; the image's default root user and missing non-root setup amplify the impact. Remediation means upgrading PHP to a fixed release and rebuilding the final image, since no configuration change in this image removes these flaws. Note: this is a general-purpose base/runtime image — many findings live in components that an application built on top may never load, so actual exploitability depends on the final image. For an accurate risk picture, re-scan the final application image with context.
Hardening plan for this image · 4 steps. The first closes 3 actively exploited CVEs.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-109618 | CRITICAL10 | php 8.5.9 No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-109619 | CRITICAL10 | php 8.5.9 No fix yet | 100.0% Actively Exploited | Directly ExposedContext importance: HIGH |
| CVE-2026-111497 | HIGH8 | brotli-libs 1.2.0-r1 fixed in 1.2.1-r0 | 55.5% Actively Exploited | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63072 | MEDIUM6 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63072 | MEDIUM6 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-63072 | MEDIUM6 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.9% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91765 | MEDIUM6 | php 8.5.9 No fix yet | 0.4% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2025-14181 | MEDIUM5.2 | php 8.5.9 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-91767 | MEDIUM5.2 | php 8.5.9 No fix yet | 0.1% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-85091 | MEDIUM5 | zlib 1.3.2-r0 fixed in 1.3.2-r1 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-91766 | MEDIUM4.72 | php 8.5.9 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-93682 | MEDIUM4.64 | php 8.5.9 No fix yet | 0.3% Theoretical Threat | Directly ExposedContext importance: MEDIUM |
| CVE-2026-14456 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-14456 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.7% Theoretical Threat | Directly Exposed |
| CVE-2026-18798 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.7% Low-Moderate Risk | Directly Exposed |
| CVE-2026-63076 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.6% Low-Moderate Risk | Directly Exposed |
| CVE-2026-14457 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-54874 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63074 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-63075 | MEDIUM4.5 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-91769 | MEDIUM4.3 | php 8.5.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl 1.2.6-r2 fixed in 1.2.6-r3 | — | Directly Exposed |
| CVE-2026-107891 | MEDIUM4 | musl-utils 1.2.6-r2 fixed in 1.2.6-r3 | — | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-19931 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 1.1% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92388 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86414 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92390 | LOW3.9 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-91768 | LOW3.9 | php 8.5.9 No fix yet | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW3.7 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.54 | libcrypto3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-86411 | LOW3.54 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-63073 | LOW3.54 | libssl3 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Directly Exposed |
| CVE-2026-92842 | LOW3.54 | php 8.5.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-6103 | LOW3.3 | php 8.5.9 No fix yet | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-58055 | LOW3.24 | nghttp2-libs 1.69.0-r0 fixed in 1.70.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86409 | LOW3.18 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86412 | LOW3.18 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86413 | LOW3.18 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92392 | LOW2.92 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-82208 | LOW2.88 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82208 | LOW2.88 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107928 | LOW2.88 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92386 | LOW2.58 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-86410 | LOW2.45 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-80256 | LOW2.4 | curl 8.21.0-r0 fixed in 8.22.0-r0 | — | Directly Exposed |
| CVE-2026-80256 | LOW2.4 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | — | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80231 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-107929 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-13608 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-18924 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80229 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.6% Theoretical Threat | Directly Exposed |
| CVE-2026-80230 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-80231 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.9% Theoretical Threat | Directly Exposed |
| CVE-2026-80255 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.5% Theoretical Threat | Directly Exposed |
| CVE-2026-86415 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87861 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87862 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87863 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-87864 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87865 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-87866 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-92387 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92389 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-92391 | LOW2.22 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-75803 | LOW2.22 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 0.3% Theoretical Threat | Post-Exploit |
| CVE-2026-63073 | LOW2.12 | openssl 3.5.7-r0 fixed in 3.5.8-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-94266 | LOW1.98 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-94266 | LOW1.98 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.2% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | curl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | curl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
| CVE-2026-82209 | LOW1.86 | libcurl 8.21.0-r0 fixed in 8.22.0-r0 | 0.4% Theoretical Threat | Directly Exposed |
| CVE-2026-94265 | LOW1.86 | libcurl 8.21.0-r0 fixed in 8.23.0-r0 | 0.3% Theoretical Threat | Directly Exposed |
Want to check another image? Run a full scan with the Docker Security Scanner.