Redis Ships Seven Emergency Patches After RCE Exploits Go Public

Researchers using Kimi K3 autonomous AI agents have published working proof-of-concept exploits for authenticated remote code execution (RCE) vulnerabilities in four actively-maintained Redis releases: 6.2.22, 7.4.9, 8.6.4, and 8.8.0. In response, the Redis project shipped seven security releases on July 23. The PoC code is already public.

What Happened

Security researchers demonstrated that Kimi K3 AI agents could independently discover and chain Redis vulnerabilities into working RCE exploits without human guidance. All known attack chains require the RESTORE command to be accessible. Two chains additionally require EVAL and XGROUP (via Streams); the chain targeting Redis 8.8.0 requires EVAL and the bundled RedisBloom module.

These are authenticated vulnerabilities — an attacker needs valid Redis credentials or direct network access to an unauthenticated instance. That second path is far more common than it should be: Redis is routinely left bound to 0.0.0.0 with no password in dev environments, containers, and misconfigured cloud deployments.

Why It Matters

Redis is load-bearing infrastructure for an enormous share of the modern web — caching layer, session store, job queue, pub/sub backbone. If it falls, the application above it typically falls with it, and any attacker with a shell on your Redis host is positioned for lateral movement into the rest of your stack.

The public PoC collapses the exploitation window to near zero. Attackers do not need to reverse-engineer the patches; a working exploit is already written and circulating. This is not a "patch this week" advisory — it is a "patch in the next hour" incident.

The version spread makes it worse. Redis 6.2.x, 7.4.x, 8.6.x, and 8.8.x are all affected, meaning no recent release branch is safe without an upgrade.

What To Do

1. Find every Redis instance you run. Check production, staging, dev, containers, and managed services. Shadow instances in forgotten namespaces are common.

2. Update immediately. The seven patched releases landed July 23. Consult the official Redis release notes for the fixed version in your branch and upgrade now.

3. Disable RESTORE if you don't use it. All exploit chains require this command. Adding rename-command RESTORE "" to redis.conf is a fast mitigation you can apply before the upgrade window opens.

4. Enforce auth and binding. If you are running Redis without requirepass or bound to 0.0.0.0, fix that right now — independently of this CVE. An open Redis is a permanent liability.

5. Tighten ACLs. Redis 6+ ACL rules let you restrict RESTORE, EVAL, and XGROUP to only the users that legitimately need them. Do it.

For managed Redis (ElastiCache, Upstash, Redis Cloud): check your provider's security bulletin. Most will patch automatically, but verify — do not assume.

Public RCE PoC against critical infrastructure is the definition of a drop-everything incident. Patch now.