Vulnerability Reportoliver006/redis_exporter:v1.97.0

oliver006/redis_exporter:latestoliver006/redis_exporter:v1.97.0

digestsha256:f5f903fbe77571d455ede0453b084d6840bc62fc105efac001034421cab83b99

Executive Summary

Last scanned: Nov 5, 2026

Threat ScoreSAFE• The threat score is 0, and no finding reaches the critical or high-risk level for this container.• The scan recorded one finding reachable from the network in normal operation, with a maximum severity of 4.0, which is low.• No finding is known to be actively exploited, and no finding matters only after the container is already compromised.• The main process is a statically linked Go program that does not load system shared libraries, so flaws in OS libraries are not reachable through it.• The image runs as a non-root user (59000:59000) and is pinned by digest, which limits both privilege and drift.• The publisher is a popular community image with the reputation verdict RELIABLE, which is noted here but did not drive the result.

0/100SAFE

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

RELIABLE

This image is safe for production use. The scan found one low-severity issue that is reachable from the network, with a maximum severity of 4.0, so it does not change the verdict. Nothing in the scan is known to be actively exploited, and the main process does not pull in system libraries where OS-level flaws would sit. Keeping the image pinned by digest and running it as a non-root user keeps the risk low, and the one finding should still be tracked in routine patching.

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

1 total

CVE ID	Adjusted Severity	Package	Exploit Probability	Risk Context
GO-2026-5932	MEDIUM4	golang.org/x/crypto v0.58.0 No fix yet	—	Directly Exposed

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