Vulnerability Reporthaproxy:3.3.15-alpine

haproxy:3.3.15-alpine

digestsha256:92cb3a3f8bcbd229ae7dff8dae897774d6448b38892b955992dc31d2ffa3e996

Executive Summary

Last scanned: Oct 21, 2026

Threat ScoreSAFE• Pre-calculated threat score is 0, placing this image in the SAFE band.• Official Docker Hub image from Docker Official, with trust score 100 and pinned by digest.• INPUT 3 reports exposed_total 1 and post_total 1, but exposed_max_severity is 0.0 and post_max_severity is 2.33.• No exposed-surface or post-exploit findings are listed in INPUT 4 or INPUT 5, and no CVE IDs are provided to cite.• No high-severity exposed findings or notable post-exploit findings are present to raise the verdict.

0/100SAFE

ReputationOFFICIAL• Official Docker Hub Image• Pinned by digest (Immutable)

TRUSTED

This image is safe for production use. Although the stats show one exposed and one post-exploit finding, the exposed max severity is 0.0 and the post-exploit max severity is 2.33, with no specific CVE details provided in the findings lists. The image is an official Docker Hub image pinned by digest with a trusted reputation, and no production-blocking risk is indicated by the provided inputs.

Vulnerabilities

Vulnerability Log

2 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
CVE-2026-103111	LOW2.33	pcre2 10.48-r0 fixed in 10.49-r0	0.2% Theoretical Threat	Post-Exploit
CVE-2026-85091	NONE0	zlib 1.3.2-r0 fixed in 1.3.2-r1	0.4% Theoretical Threat	Not Applicable

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.