Vulnerability Reporthaproxy:2.8.28-alpine

haproxy:2.8.28-alpine

digestsha256:e0d1dc5a92d389551a968627602fcd64b038af819b496c9636bbc38a3cf745b4

Executive Summary

Last scanned: Oct 21, 2026

Threat ScoreSAFE• Threat score is 0, placing this image in the SAFE band.• Official Docker Official image, pinned by digest, with trust verdict TRUSTED and score 100.• Vulnerability stats show exposed_total 1 and post_total 1, but exposed_count_ge6 is 0, exposed_count_ge7 is 0, and exposed_max_severity is 0.0.• Post-exploit stats show post_count_ge6 is 0 and post_max_severity is 2.33, which is below the NEEDS_ATTENTION threshold.• No CVE IDs are present in the provided top exposed-surface or post-exploit findings.

0/100SAFE

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

TRUSTED

This image is safe for production use. The stats show one exposed entry and one post-exploit-only entry, but their maximum severities are 0.0 and 2.33 respectively, with none at or above 6.0. This image is an official Docker image pinned by digest, which supports its trusted reputation. The low-severity findings do not change the SAFE verdict for this container.

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.