Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. A remote attacker who reaches port 6379 could corrupt memory and possibly execute code on the Redis server, gaining control over the data it stores and serves. The default configuration has no password and accepts remote clients, so these high-severity flaws are reachable in normal operation, and running as root would widen the damage. Do not deploy this image in any production role; it must be rebuilt on a patched Redis release with authentication enforced and network access restricted.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-23479 | HIGH8.8 | redis 7.4.12 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-25243 | HIGH8.8 | redis 7.4.12 No fix yet | 4.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-23631 | MEDIUM6.48 | redis 7.4.12 No fix yet | 3.1% Low-Moderate Risk | Directly ExposedContext importance: MEDIUM |
Which CVEs are actually reachable — is the vulnerable code even linked and callable.
Live-container probes: default user, writable paths, capabilities, exposed ports.
Base-image lineage, package provenance and signatures — nothing slipped in unnoticed.
A step-by-step hardened build plan, with parity tests proving nothing breaks.
Want to check another image? Run a full scan with the Docker Security Scanner.