Vulnerability Reportphp:8.2.35-cli-alpine3.23

php:8.2.35-cli-alpine3.23php:8.2.35-alpine3.23php:8.2-cli-alpine3.23php:8.2-alpine3.23
digestsha256:198ed9e076a5c6ad8c17b64c3ff874c276a5e86527a9888f07eee837bc862040

Executive Summary

Last scanned:

Threat Score
54/100CAUTION
Reputation
TRUSTED

This base/runtime image carries significant vulnerabilities that any image built on it would inherit; remediate them in the final image before production. The main concern is CVE-2026-111497, a high-severity memory corruption flaw in the Brotli decoder that could allow code execution in the PHP process if an application feeds it untrusted compressed data. Note: CVE-2026-111497 only applies when a downstream application or linked library decodes attacker-supplied Brotli data, which is not a default behavior of this interactive PHP shell image. Not passing untrusted Brotli input to the decoder in images built on top of this one would fully eliminate this specific risk. 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.

Vulnerabilities

Vulnerability Log

49 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-111497HIGH7.45
brotli-libs
1.2.0-r0
fixed in 1.2.1-r0
36.0%
High Exploitation Risk
Directly ExposedContext importance: MEDIUM
CVE-2026-92392LOW2.92
curl
8.22.0-r0
fixed in 8.23.0-r0
1.3%
Low-Moderate Risk
Post-Exploit
CVE-2026-92392LOW2.92
libcurl
8.22.0-r0
fixed in 8.23.0-r0
1.3%
Low-Moderate Risk
Post-Exploit
CVE-2026-107928LOW2.88
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-107928LOW2.88
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-92386LOW2.58
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-92386LOW2.58
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-86410LOW2.45
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-86410LOW2.45
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-92388LOW2.34
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-86414LOW2.34
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-92390LOW2.34
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-92388LOW2.34
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-86414LOW2.34
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-92390LOW2.34
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-107929LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-86415LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87861LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87862LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-87863LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87864LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87865LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87866LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-92387LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-92389LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-92391LOW2.22
curl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-107929LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-86415LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87861LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87862LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-87863LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87864LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87865LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-87866LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-92387LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-92389LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-92391LOW2.22
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-86411LOW2.12
curl
8.22.0-r0
fixed in 8.23.0-r0
0.1%
Theoretical Threat
Post-Exploit
CVE-2026-86411LOW2.12
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.1%
Theoretical Threat
Post-Exploit
CVE-2026-94266LOW1.98
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-94266LOW1.98
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly Exposed
CVE-2026-86409LOW1.91
curl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-86412LOW1.91
curl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-86413LOW1.91
curl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-86409LOW1.91
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-86412LOW1.91
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Post-Exploit
CVE-2026-86413LOW1.91
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Post-Exploit
CVE-2026-94265LOW1.86
curl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed
CVE-2026-94265LOW1.86
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly Exposed

Reachability analysis

Which CVEs are actually reachable — is the vulnerable code even linked and callable.

Locked

Runtime verification

Live-container probes: default user, writable paths, capabilities, exposed ports.

Locked

Supply chain analysis

Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.

Locked

Hardening recommendations

A step-by-step hardened build plan, with parity tests proving nothing breaks.

Locked

Want to check another image? Run a full scan with the Docker Security Scanner.