« All posts

Authenticated RCE Exploits Hit Redis via Stream, TDigest, TopK Bugs

Authenticated RCE chain hits Redis 6.2.22 through 8.8.1 via stream NACK double-free, TDigest and TopK module bugs, bypassing two prior CVE patches.

A new exploit toolkit demonstrates authenticated remote code execution against multiple Redis releases (6.2.22, 7.4.9, 8.6.4, 8.8.0, 8.8.1), chaining a stream consumer-group shared-NACK double-free, a TDigest heap overflow, and a TopK wild-free bug in the bundled RedisBloom module. Two of the exploits are direct patch bypasses: one defeats the CVE-2026-25243 fix, the other circumvents CVE-2026-25589 by exploiting incomplete pointer zeroing in TopK_Destroy.

Each exploit only needs commands already available to authenticated users — EVAL, RESTORE, and XGROUP — plus the RedisBloom module shipped by default in 8.8.x. Reliability figures range from 5/5 to 25/25 across fresh containers, though the 8.8.0/8.8.1 exploits are jemalloc-layout sensitive and require isolated instances free of concurrent traffic.

For engineers running Redis in production, this shows that authentication alone is not a sufficient trust boundary once clients can issue RESTORE, EVAL, or module-backed commands; version pinning and CVE patches may not fully close this class of memory-corruption bugs. The toolkit is explicitly framed for authorized testing, but its existence highlights the exposure of self-hosted Redis deployments that expose these commands to less-trusted clients.

This synthesis was produced from its source by AI; there is no human editor or manual review step. How we work