Vulnerability Reportzabbix/zabbix-proxy-sqlite3:latest

zabbix/zabbix-proxy-sqlite3:latestzabbix/zabbix-proxy-sqlite3:7.4-alpine-latestzabbix/zabbix-proxy-sqlite3:alpine-7.4-latest
digestsha256:4ddc2d2c8ef833d8a587c58397a7966b31034d7068557f74510386d3f5ec88b5

Executive Summary

Last scanned:

Threat Score
28/100NEEDS ATTENTION
Reputation
TRUSTED

This image is acceptable for production, but remediating the identified vulnerabilities is recommended to reduce the attack surface. The scan reports 17 exposed-surface findings and 7 post-exploit findings, and acknowledging them is important even though they do not raise the verdict. The main concern is CVE-2026-92392, a libcurl HTTP/2 flaw with a maximum severity of 6.48 that could be triggered when the proxy makes outbound HTTP/2 requests to a malicious server. The scan states no special configuration is required for this issue, so it is relevant to typical deployments. Updating libcurl in the image is the most direct way to reduce this exposure.

Vulnerabilities

Vulnerability Log

24 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-92392MEDIUM6.48
libcurl
8.22.0-r0
fixed in 8.23.0-r0
1.3%
Low-Moderate Risk
Directly ExposedContext importance: MEDIUM
CVE-2026-86414MEDIUM5.2
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-107928LOW3.84
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-92386LOW3.44
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-107929LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-86415LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-87861LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-87862LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-87863LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-87864LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-87865LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-87866LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-92387LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-92389LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-92391LOW2.96
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-94266LOW2.64
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.2%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
CVE-2026-94265LOW2.48
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.3%
Theoretical Threat
Directly ExposedContext importance: MEDIUM
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
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-86411LOW2.12
libcurl
8.22.0-r0
fixed in 8.23.0-r0
0.1%
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

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.