AI agents just did what security researchers have warned about for years: a swarm of 32 Kimi K3 agents autonomously discovered authenticated remote code execution (RCE) vulnerabilities in Redis and built a working exploit chain for Redis 8.8.0 in just 27 minutes. Redis shipped patches on July 23, and public proof-of-concept code is already on GitHub. The exploit window is open.

What Happened

Moonshot AI’s Kimi K3 — a 2.8-trillion-parameter model that recently topped SWE-bench Pro — was used in an autonomous multi-agent security research run. Researcher Chaofan Shou reported on X that 32 agents working in parallel found 19 Redis zero-days in roughly 90 minutes, with a full exploit chain for Redis 8.8.0 produced in just 27 minutes. Redis’s July 23 advisory confirms the bugs and patches, though it does not validate the claimed zero-day count or the degree of agent autonomy. The timing should be taken as directionally accurate rather than lab-certified.

What isn’t in dispute: authenticated RCE vulnerabilities exist in Redis 6.2.22, 7.4.9, 8.6.4, and 8.8.0. Public PoC code is available on GitHub. Redis has released fixes. That combination alone makes this urgent.

Both exploit chains share a common entry point: the RESTORE command. Beyond that, they hit different parts of the codebase, including a Stream NACK double-free bug. Redis shipped seven security releases across the four affected versions on July 23.

Read the full announcement →

My Take

This is the kind of event security researchers have been warning about for years. The fear was always that AI agents would eventually automate the discovery of zero-days faster than humans could patch them. That future is now here. Twenty-seven minutes to find and weaponize a critical vulnerability in a widely-used database is a pace that manual security teams cannot match.

For developers and infrastructure teams, the immediate action is clear: patch Redis now. All four affected versions have fixes available. But the longer-term implication is more unsettling. We’re entering an era where the speed of vulnerability discovery is measured in minutes, not weeks. Security patching strategies that involve monthly cycles or “wait for validation” are now obsolete. The window between disclosure and exploitation has effectively collapsed.

What to Watch

  • How quickly attackers weaponize these PoCs — public code is already out, and automated scanning will follow fast.
  • Kimi K3’s impact on vulnerability research — if this becomes a repeatable pattern, expect more zero-days from other critical infrastructure (e.g., PostgreSQL, Nginx, OpenSSL).
  • The arms race between agent-driven discovery and automated patch deployment — expect tooling like live-patching and automatic hotfix rollouts to become table stakes.