Vulnerability Reportvalkey/valkey:9.2-alpine

valkey/valkey:9.2-alpine3.24valkey/valkey:9.2-alpine
digestsha256:cdcb7b1c7b6f1c9cb9442c71ac6275e78184657448407b2c1fdde7ee8024f4fb

Executive Summary

Last scanned:

Threat Score
1/100SAFE
Reputation
RELIABLE

This image is safe for production use. The scan found 3 low-severity issues, with the highest rated 5.0, and none of them is known to be actively exploited or to be serious in this container's normal operation. Those findings do not change the verdict, but keeping the image updated as new releases come out is still good practice. Because the server runs as root by default, running it with a non-root user would further limit damage if a future flaw were found.

Already in good shape · 2 hardening steps left

Included in Pro

Scanning procedure

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

Vulnerabilities

Vulnerability Log

3 total
CVE IDAdjusted SeverityPackageExploit ProbabilityRisk Context
CVE-2026-85091MEDIUM5
zlib
1.3.2-r0
fixed in 1.3.2-r1
0.5%
Theoretical Threat
Directly Exposed
CVE-2026-107891MEDIUM4
musl
1.2.6-r2
fixed in 1.2.6-r3
—
Directly Exposed
CVE-2026-107891MEDIUM4
musl-utils
1.2.6-r2
fixed in 1.2.6-r3
—
Directly Exposed

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