Vulnerability Reportprom/prometheus:v3.13.2

prom/prometheus:v3.13.2prom/prometheus:v3.13.2-busybox

digestsha256:508729e0e2d18e11fd742a5a5ca70e557b940a93948c3c95fd0123a6fd538b69

Executive Summary

Last scanned: Aug 19, 2026

Threat ScoreSAFE• High-reputation community image with 1.99B pulls and pinned by digest (immutable).• Threat score is 0, well within the safe range.• Only 1 exposed finding with maximum severity 0.0, no actionable vulnerabilities.• No post-exploit findings are reported.• No high-severity or critical vulnerabilities present.

0/100SAFE

ReputationPOPULAR COMMUNITY• High Reputation Community Image (1991M+ pulls)• Pinned by digest (Immutable)

RELIABLE

This image is safe for production use. The sole exposed finding has a severity score of 0.0, presenting no practical risk to the Prometheus service. No post-exploit vulnerabilities are reported. The image's high community trust and immutable digest further support its safe deployment.

Relevant for prom/prometheus:v3.13.2

Most CVEs in Go images aren't exploitable

This image is a Go binary — most findings can be ruled out with three commands. How to prove which ones are real.

Read the article

Vulnerabilities

Vulnerability Log

1 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
GO-2026-5932	NONE0	golang.org/x/crypto v0.53.0 No fix yet	—	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.