Vulnerability Reporthaproxy:2.6.33-alpine

haproxy:2.6.33-alpine

digestsha256:5cc4558a47b4d795a2561a6f249038168ad114aac29380c3e5e161fd53c8d655

Executive Summary

Last scanned: Oct 21, 2026

Threat ScoreSAFE• Threat score is 0, placing this image in the SAFE band (0-24).• Trust checks show an official Docker Hub image pinned by digest with trust score 100.• Vulnerability stats show exposed_total 1 and post_total 1, but exposed_count_ge6 is 0 and post_count_ge6 is 0.• Maximum exposed severity is 0.0 and maximum post-exploit-only severity is 2.33, below the attention thresholds.• No CVE IDs or detailed findings are present in INPUT 4 or INPUT 5 to support elevated risk.

0/100SAFE

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

TRUSTED

This image is safe for production use. The stats list one exposed-surface item and one post-exploit-only item, but exposed_count_ge6 and post_count_ge6 are both 0, with max severities of 0.0 and 2.33 respectively. No CVE details are present in the top findings, and the official Docker image is pinned by digest with a trust score of 100. These low-severity or undetailed findings do not change the SAFE verdict.

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.