Vulnerability Reportprom/prometheus:latest

prom/prometheus:latestprom/prometheus:v3prom/prometheus:v3-busyboxprom/prometheus:latest-busyboxprom/prometheus:v3.15.1prom/prometheus:v3.15.1-busybox

digestsha256:fa3302279710be2f21a8301ec17a8b4f2301fd829bd113839b3b6b02b6f191a2

Executive Summary

Last scanned: Oct 22, 2026

Threat ScoreSAFE• The image has a high reputation, being a popular community image with over 2 billion pulls.• Vulnerability scanning found only 1 exposed vulnerability, but it is not high severity.• No critical or high-severity findings were identified in the exposed or post-exploit surfaces.

0/100SAFE

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

RELIABLE

This image is safe for production use. The image is highly popular and maintained by a reputable community. While one exposed vulnerability was detected, the overall threat score is low, and no critical risks were identified in the exposed or post-exploit surfaces.

Relevant for prom/prometheus:latest

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.57.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.