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 reaches port 6379 could execute code on the server, corrupt memory, or disrupt the cache service, because no password is set and protected mode is off. Note: CVE-2026-23631 only applies if a master-replica setup with writable replicas is used. Upgrading Redis to 8.6.3 or later addresses the affected versions of CVE-2026-23479.
| CVE ID | Adjusted Severity | Package | Exploit Probability | Risk Context |
|---|---|---|---|---|
| CVE-2026-23479 | HIGH8.8 | redis 8.4.8 No fix yet | 1.7% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-25243 | HIGH8.8 | redis 8.4.8 No fix yet | 4.0% Low-Moderate Risk | Directly ExposedContext importance: HIGH |
| CVE-2026-23631 | MEDIUM6.48 | redis 8.4.8 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.