Vulnerability Reporttraefik:v3.7.16

traefik:v3.7.16traefik:3.7.16

digestsha256:1336e85aaed293bd63d005086e0dd013b04078b26aaeb1c18b26a2f928af7e65

Executive Summary

Last scanned: Nov 1, 2026

Threat ScoreSAFE• Trusted official Docker Hub image with publisher Docker Official and trust score 100.• Image is pinned by digest, supporting immutability and reducing tag-mutation risk.• Provided vulnerability stats show exposed_total 0 and post_total 0, with no exposed or post-exploit findings listed.• Threat score is 0, which maps to the SAFE band under the provided scoring.• No CVE IDs are present in the supplied findings, so no specific vulnerability mitigations are required from these inputs.

0/100SAFE

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

TRUSTED

This image is safe for production use. It is an official Docker Hub image pinned by digest, which supports supply-chain trust. The provided stats show exposed_total 0 and post_total 0, and no CVE findings appear in the supplied exposed or post-exploit lists. No compensating controls are required based on these inputs, though routine digest refresh and monitoring remain prudent.

Already in good shape · 1 hardening step left

Included in Pro

Scanning procedure

Vulnerability scan
Full CVE sweep across OS packages and app dependencies
Exploitability check
CVEs ranked by exploit probability (EPSS) and matched against CISA KEV
Reachability analysis
Symbol-level proof: is the vulnerable code even linked and callable in your binaries?
Runtime verification
Live-container probes: exposed endpoints, feature flags, real defaults
Supply chain analysis
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed
Hardening recommendations
A hardened build plan — patch, remove unused packages, lock down the runtime — with parity tests proving nothing broke

Vulnerabilities

Vulnerability Log

0 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
No vulnerabilities found matching filters.

Want to check another image? Run a full scan with the Docker Security Scanner.