Redis Patches Two-Year-Old Use-After-Free Surfaced by Autonomous AI Bug Hunter

Redis has shipped patches for a use-after-free in its blocking-client handling that allows an authenticated user to execute arbitrary operating-system commands on the host. The bug is tracked as CVE-2026-23479.

It was introduced in Redis 7.2.0. It survived every stable branch until the fixes landed on May 5. That is more than two years of exposure across production deployments.

What sets this disclosure apart is the finder. The flaw was surfaced by an autonomous AI tool designed to audit large codebases for memory-safety defects, not by a human researcher reading diffs. The discovery sits in a category regulators have started watching closely as AI-assisted vulnerability research moves from demo to practice.

The technical shape is familiar to anyone who has read Redis CVE history. A use-after-free in the path that handles blocking clients gives an authenticated attacker a primitive strong enough to pivot into command execution on the underlying host. Authentication is required, but Redis instances frequently sit behind weak boundary controls, exposed to internal applications that themselves can be compromised. The CVSS scoring and full vendor write-up will determine where this lands on patch-priority lists.

A few points operators should note.

First, the affected version range begins at 7.2.0. Anything earlier is out of scope for this specific CVE, though older branches carry their own backlog. Second, the fix shipped May 5 across maintained branches; downstream distributions and managed-service providers will follow on their own cadence. AWS ElastiCache, Azure Cache for Redis, and Google Memorystore customers should consult their provider advisories for the patched build identifier before assuming coverage.

There is no proposed rulemaking attached to this disclosure, but the provenance matters for ongoing policy debates. CISA's Secure by Design pledge and the EU Cyber Resilience Act both contemplate vendor obligations around vulnerability discovery and disclosure. Neither framework currently distinguishes between human-found and machine-found defects. That distinction will become harder to ignore as autonomous tools file a larger share of valid reports — and as the question of who is the "reporter" of record under coordinated disclosure norms gets pressed.

For now, the operational guidance is straightforward. Inventory Redis instances. Confirm the running version. Apply the May 5 patch or a later build. Audit which application identities hold authenticated access, and whether any of those identities are reachable from untrusted network segments.

The CVE record on NVD remains the authoritative reference as enrichment data populates over the coming days.