Last scanned:
··This image is safe for production use. The scan found 48 vulnerabilities, but none are reachable from the network in normal operation, and the highest severity among them is low (2.92). They would only matter if an attacker had already compromised the container, so they do not change the verdict. Keeping the image updated with future Zabbix releases is still good practice.
Already in good shape · 3 hardening steps left
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-92392 | LOW2.92 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92392 | LOW2.92 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 1.3% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-86410 | LOW2.45 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-92388 | LOW2.34 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86414 | LOW2.34 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92390 | LOW2.34 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-86411 | LOW2.12 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86411 | LOW2.12 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86412 | LOW1.91 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-86413 | LOW1.91 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86409 | LOW1.91 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 1.1% Low-Moderate Risk | Post-Exploit |
| CVE-2026-86412 | LOW1.91 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-86413 | LOW1.91 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-107928 | LOW1.73 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92386 | LOW1.55 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-92386 | LOW1.55 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-107929 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86415 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87861 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-87862 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-87863 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-92387 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-107929 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-86415 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.4% Theoretical Threat | Post-Exploit |
| CVE-2026-87861 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-87862 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 1.0% Theoretical Threat | Post-Exploit |
| CVE-2026-87863 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-87864 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-87865 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-87866 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.5% Theoretical Threat | Post-Exploit |
| CVE-2026-92387 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 1.0% Low-Moderate Risk | Post-Exploit |
| CVE-2026-92389 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.7% Theoretical Threat | Post-Exploit |
| CVE-2026-92391 | LOW1.33 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 1.2% Low-Moderate Risk | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-94266 | LOW1.19 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.6% Theoretical Threat | Post-Exploit |
| CVE-2026-94265 | LOW1.12 | curl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
| CVE-2026-94265 | LOW1.12 | libcurl 8.22.0-r0 fixed in 8.23.0-r0 | 0.8% Theoretical Threat | Post-Exploit |
Want to check another image? Run a full scan with the Docker Security Scanner.