Skip to content
feed: live
>_ 0dayNews
cloud

AI Agents Uncover Redis Zero-Days, Seven Patches Ship

Kimi K3 AI agents found authenticated RCE flaws in four Redis versions. Redis shipped seven security releases on July 23 — update your deployments.

AI Agents Uncover Redis Zero-Days, Seven Patches Ship
Photo: Boris Carmi / Wikimedia Commons · CC BY 4.0
kilobaud Dave "Kilobaud" Ferris · Published · 2 min read

Redis shipped seven security releases on Wednesday after researchers used Kimi K3 AI agents to find memory safety flaws in four versions and publish proof-of-concept exploit code. The affected builds — 6.2.22, 7.4.9, 8.6.4, and 8.8.0 — have patches available. If you’re running any of them, that’s the sentence this article is about.

The Hacker News report describes the AI agents not just finding the vulnerabilities but constructing the exploits. Redis’s own characterization of the underlying issues is more cautious — memory flaws that “may lead to remote code execution” — which is the standard vendor language for confirmed bugs before an adversarial PoC gets refined into something cleaner. The PoCs are public.

The patch situation

Seven releases shipped simultaneously across the affected branches on July 23. The update targets are Redis 6.2.23, 7.2.15, and 7.4.10, plus current 8.x builds. Redis’s security advisory page has the details.

Exploitation in these cases requires authentication — authenticated RCE, not unauthenticated. That matters for surface exposure. Redis instances behind private network access and strong auth have meaningful defense-in-depth. Instances where authenticated access is granted broadly to internal services, or where client credentials are weak or reused, are more exposed than the “requires auth” framing implies.

The research method

Kimi K3 is a reasoning AI from Moonshot AI. The notable thing about this disclosure isn’t the bug class — memory safety in a C-family codebase has been a known category for decades — it’s how fast the discovery cycle ran. An AI agent reviewed Redis’s source and surfaced exploitable flaws at a pace no human audit schedule would match.

That’s not alarming when the researchers coordinate with the vendor and the vendor patches before widespread exploitation. That’s the disclosure process working correctly.

The part worth sitting with is that the same research pattern — AI agents running structured source analysis and building proof-of-concept exploits — is available to threat actors who don’t coordinate with anyone. The asymmetry that defined responsible disclosure was always about time and expertise. AI is compressing both.

Why Redis specifically

Redis is widely deployed as a cache, session store, and message broker across production infrastructure — cloud and on-premises. An instance sitting between a web application and its database, holding session tokens or queued jobs, is a useful foothold. Seven patches shipping in a day is a good sign the vendor took this seriously. The patch window, as usual, belongs to whoever updates fastest.


Related: OpenAI Eval Reached HuggingFace Production · AI Is Now Both Attack Tool and Attack Surface · Dolphin X RAT Uses AI to Score High-Value Targets

Found this useful? Share it.