Kimi K3 Agents Found Redis Zero-Days and Built RCE Exploit, Researchers Say

Redis shipped seven security releases on July 23 after researchers published authenticated RCE PoCs for stock Redis 6.2.22, 7.4.9, 8.6.4, and 8.8.0. All four chains require RESTORE. The Streams chains also need EVAL and XGROUP; the 8.8.0 chain needs EVAL and the bundled RedisBloom module. Redis says the underlying memory flaws may lead to remote code execution. Redis 6.2.23, 7.2.15, and 7.4.10

Report facts: researchers say Kimi K3 used multiple agents to find Redis flaws and produce authenticated RCE proof-of-concepts against stock Redis builds, with affected paths involving commands such as RESTORE, EVAL, and XGROUP, plus a RedisBloom/TDigest issue in the latest branch. Redis released multiple security fixes on July 23, including branch-specific updates and guidance to restrict dangerous commands and block untrusted network access.[1][2][4] RealGround analysis: this is best classified as AI agent abuse because the story demonstrates an autonomous agent being used to discover and weaponize vulnerabilities; the practical control focus is on agent governance, red-team validation, and secure build guardrails for offensive-capable AI workflows.