Autonomous AI Tool Finds 2-Year-Old RCE Flaw in Redis (CVE-2026-23479)
Redis patched CVE-2026-23479, a two-year-old use-after-free that can let authenticated attackers run OS commands on the host.
Intelligence analysis by GPT-5.4 Mini
An autonomous AI bug-hunting tool found a Redis use-after-free introduced in 7.2.0 and left in stable releases for more than two years. The published exploit chain can turn an authenticated session into OS command execution, with cloud deployments making exposure worse.
A hidden mistake in Redis was like a door that still tried to use a key after the key had already been thrown away. Someone with the right pass could trick it into opening the wrong door and make the computer run a command.
Analysis
What was found
Redis fixed CVE-2026-23479, a use-after-free in its blocking-client path that can let an authenticated user execute operating-system commands on the host running the database. The bug was introduced in Redis 7.2.0 and survived across stable branches for over two years before being patched on May 5.
How the issue works
The flaw sits in unblockClientOnKey() in src/blocked.c. According to the write-up, the function calls processCommandAndResetClient(), then keeps using the same client pointer even though that helper can free the client as a side effect. That creates a classic use-after-free. Wiz and the technical write-up describe a chain that first leaks a heap address, then frees a client and replaces it in memory, and finally uses Redis memory-accounting logic to overwrite a function pointer.
Why the impact is serious
The reported path ends with command execution by steering strcasecmp() toward system(). The article says the official Redis Docker image is easier to abuse because it leaves the GOT writable at runtime under partial RELRO. ASLR and PIE do not block the chain because the overwrite is relative to a global offset fixed at build time.
Exposure and mitigation
The exploit requires an authenticated session with commands such as CONFIG SET, EVAL, stream operations, and basic read/write access. In many deployments, the default Redis user already has those permissions, which makes the chain practical in common cloud setups. Redis says there is no evidence of exploitation in its own or customer environments, but the full technical chain is now public. The article recommends upgrading to the fixed minors: 7.2.14, 7.4.9, 8.2.6, 8.4.3, or 8.6.3. If patching is delayed, it advises keeping Redis off the public internet, tightening ACLs, and denying Lua scripting where it is not needed.
Key points
- CVE-2026-23479 is a Redis use-after-free that can lead to remote command execution for authenticated attackers.
- The bug was introduced in Redis 7.2.0 and stayed in stable branches for more than two years.
- The published exploit chain uses heap leakage, client reallocation, and memory-accounting abuse to reach code execution.
- Default Redis deployments can be especially exposed because common roles already include the needed permissions.
- Redis has released fixed minors, and the article recommends upgrading or tightening ACLs and network exposure.
The flaw is patched in current minor releases, and the article says minor upgrades are meant to be drop-in. Managed services can also absorb the fix on their own schedules, with Redis saying Redis Cloud is already done.
Unpatched Redis instances, especially internet-exposed ones with shared credentials and broad roles, remain attractive targets. The public exploit chain could make follow-on attacks easier until operators upgrade and tighten ACLs.
