Security update: Redis response to the Kimi K3 vulnerability claims | Redis

This post details Redis's response to the Kimi K3 vulnerability claims, specifically addressing three identified issues: a Redis Streams shared-NACK use-after-free, a RedisBloom TDigest out-of-bounds write, and a RedisBloom TopK RDB loader wild-free. It notes that these were duplicates of issues already reported via the bug bounty program. The post announces expedited open-source fixes for two issues (Redis 8.8.1 and older branches, plus RedisBloom security releases) and that the TopK issue has been remediated in Redis Software and Redis Cloud, with an open-source update forthcoming. It also reiterates best practices for securing Redis instances, such as strong authentication, ACLs, and network access restrictions.