Ethical Hacking News
Kimi K3 agents have discovered multiple Redis zero-days, including a critical vulnerability that can be exploited using the RESTORE command. This discovery highlights the need for database security patches and best practices to prevent potential remote code execution. To stay ahead of emerging threats, it is essential to prioritize continuous vulnerability monitoring and adherence to established security protocols.
Redis zero-days were recently discovered by Kimi K3 agents, posing a risk of remote code execution (RCE) and database security breaches. The four affected Redis versions are 6.2.22, 7.4.9, 8.6.4, and 8.8.0, which require specific commands for exploitation. A total of seven security releases were shipped by Redis on July 23 to address the vulnerabilities. Researchers emphasized the importance of upgrading to the fixed release and revoking unnecessary access to prevent exploitation. The discovery highlights the significance of continuous vulnerability monitoring and patching, as well as prioritizing database security best practices.
The recent revelation by Kimi K3 agents regarding Redis zero-days has sent shockwaves throughout the cybersecurity community, highlighting the potential for remote code execution (RCE) and database security breaches. The discovery was made public on July 24, 2026, after researchers published authenticated RCE proof-of-concepts (PoCs) for stock Redis versions 6.2.22, 7.4.9, 8.6.4, and 8.8.0.
According to the findings, all four chains require the RESTORE command, while the Streams chain also necessitates the EVAL and XGROUP commands. Notably, the 8.8.0 chain requires both EVAL and the bundled RedisBloom module. The underlying memory flaws discovered in these versions may lead to remote code execution, making them vulnerable to exploitation.
In response to this vulnerability, Redis shipped seven security releases on July 23, including fixes for Streams shared-NACK use-after-free (Redis 6.2.23, 7.2.15, and 7.4.10), the RedisBloom TDigest Chain (Redis 8.2.8, 8.4.5, and 8.6.5), and the RedisBloom and TDigest loaders (Redis 8.8.1). These updates aim to address the memory corruption issues associated with the Streams Shared-NACK bug and the out-of-bounds write in the TDigest RDB loader.
It is essential to note that both Redis's July 23 release notes and the public PoC repositories reviewed did not report any in-the-wild exploitation as of July 24, 2026. However, researchers emphasize the importance of upgrading to the fixed release for the deployed branch and revoke RESTORE from accounts that do not strictly need it, blocking untrusted network access.
The Redis Streams path involves a shared-ownership bug where a corrupt RDB object can make two consumers point to the same pending-entry record, leading to double-free issues. The published script designed to turn this into arbitrary memory access ultimately invokes system(). In contrast, the RedisBloom TDigest Chain features an out-of-bounds write in the TDigest RDB loader, which allocated memory from one serialized value but trusted a separate attacker-controlled capacity field.
The Kimi K3 agents' discovery highlights the significance of continuous vulnerability monitoring and patching. The recent exploitation of the Redis zero-days underscores the need for organizations to prioritize database security, adhering to best practices such as keeping software up-to-date, restricting unnecessary access, and implementing robust network controls.
In conclusion, the revelation by Kimi K3 agents regarding Redis zero-days has underscored the importance of addressing potential vulnerabilities in database systems. As cybersecurity threats continue to evolve, it is crucial for organizations to remain vigilant and proactive in their efforts to protect against exploitation.
Related Information:
https://www.ethicalhackingnews.com/articles/Kimi-K3-Agents-Unveil-Redis-Zero-Days-A-Threat-to-Database-Security-ehn.shtml
https://thehackernews.com/2026/07/kimi-k3-agents-found-redis-zero-days.html
Published: Fri Jul 24 04:53:12 2026 by llama3.2 3B Q4_K_M
