Vulnerability Reportoliver006/redis_exporter:v1.90.0

oliver006/redis_exporter:v1.90.0

digestsha256:a129504e65b87c54f79bc92f1afc403475e8ff646a3d7512de469904ceddf986

Executive Summary

Last scanned: Oct 20, 2026

Threat ScoreSAFE• Threat score 0 falls in the SAFE band (0-24), with no DANGEROUS, CAUTION, or NEEDS_ATTENTION scoring factors triggered by the provided inputs.• Vulnerability stats list exposed_total 6 and post_total 10, but max severities are only 2.8 and 2.29, below the attention thresholds.• Inputs 4 and 5 contain no top exposed-surface or post-exploit findings, so no CVE IDs are available to cite and no high-severity exploit path is described.• Trust signals are positive: popular community image, 163M+ pulls, pinned by digest, and reputation verdict RELIABLE.• Startup command is /redis_exporter with no environment keys, and no risky configuration is identified in the provided context.

0/100SAFE

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

RELIABLE

This image is safe for production use. Input 3 reports 6 exposed and 10 post-exploit entries, but their maximum severities are 2.8 and 2.29, so they do not raise the verdict above SAFE. No CVE IDs or top findings were provided in Inputs 4 or 5, so no specific vulnerability is cited as a material production risk. The image is a widely pulled community redis_exporter pinned by digest, which supports production use with standard container hardening.

Vulnerabilities

Vulnerability Log

16 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
CVE-2026-56857	LOW2.8	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.5% Theoretical Threat	Directly Exposed
CVE-2026-78667	LOW2.29	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.4% Theoretical Threat	Post-Exploit
CVE-2026-78669	LOW2.29	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.6% Theoretical Threat	Post-Exploit
CVE-2026-97031	LOW2.29	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.4% Theoretical Threat	Post-Exploit
CVE-2026-56866	LOW1.99	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.3% Theoretical Threat	Post-Exploit
CVE-2026-94439	LOW1.99	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.3% Theoretical Threat	Post-Exploit
CVE-2026-94448	LOW1.87	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.2% Theoretical Threat	Post-Exploit
CVE-2026-97032	LOW1.81	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.4% Theoretical Threat	Post-Exploit
CVE-2026-56855	LOW1.62	golang.org/x/crypto v0.55.0 fixed in 0.56.0	0.5% Theoretical Threat	Post-Exploit
CVE-2026-78662	LOW1.62	golang.org/x/crypto v0.55.0 fixed in 0.56.0	0.4% Theoretical Threat	Post-Exploit
CVE-2026-78663	LOW1.62	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.6% Theoretical Threat	Post-Exploit
GO-2026-5932	NONE0	golang.org/x/crypto v0.55.0 No fix yet	—	Not Applicable
CVE-2026-78659	NONE0	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.6% Theoretical Threat	Not Applicable
CVE-2026-78660	NONE0	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.3% Theoretical Threat	Not Applicable
CVE-2026-94440	NONE0	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.4% Theoretical Threat	Not Applicable
CVE-2026-97030	NONE0	stdlib v1.26.7 fixed in 1.26.9, 1.27.2	0.2% 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.