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 send crafted requests to execute code inside the Redis container or crash and take over the Redis process, disrupting the data store and anything depending on it. The most serious finding, CVE-2026-25243, is exploitable by default because RESTORE is enabled and the default user has no password. The root user and disabled protected mode make the consequences of a successful attack more severe.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-23479 | HIGH8.8 | redis 7.2.17 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-25243 | HIGH8.8 | redis 7.2.17 No fix yet | 4.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-23631 | MEDIUM4.86 | redis 7.2.17 No fix yet | 3.1% Low-Moderate Risk | Directly Exposed |
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.