Last scanned:
This image poses a critical security risk and must not be used in production, especially as an internet-facing service. An attacker who can reach port 6379 could crash the Redis server or run code on the host through memory corruption, exploiting CVE-2026-23479 and CVE-2026-25243, which are reachable in normal operation because the default user has no password and remote clients are accepted. Note: CVE-2026-23631 only applies if the server is configured as a writable replica with Lua scripting enabled, so it is less relevant to a standard standalone deployment. Because the container also runs as root, a successful compromise would have a broader impact on the host environment.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-23479 | HIGH8.8 | redis 8.2.11 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-25243 | HIGH8.8 | redis 8.2.11 No fix yet | 4.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-23631 | MEDIUM6.48 | redis 8.2.11 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.