Executive Summary
In July 2026, researchers utilizing Moonshot AI's Kimi K3 agents identified multiple zero-day vulnerabilities in Redis versions 6.2.22, 7.4.9, 8.6.4, and 8.8.0. These vulnerabilities allowed authenticated remote code execution (RCE) through the RESTORE command, with additional dependencies on EVAL, XGROUP, and the RedisBloom module in certain versions. Redis promptly released seven security updates on July 23, 2026, to address these critical flaws. Organizations using affected Redis versions are urged to upgrade immediately to mitigate potential exploitation risks. (eweek.com)
This incident underscores the accelerating role of AI in both discovering and potentially exploiting software vulnerabilities. The rapid identification and proof-of-concept development by AI agents highlight the need for organizations to enhance their security posture and response times to emerging threats. (news.shield53.com)
Why This Matters Now
The swift discovery and exploitation of Redis vulnerabilities by AI agents like Kimi K3 demonstrate the evolving threat landscape, where AI accelerates both attack and defense mechanisms. Organizations must adapt by implementing robust security measures and staying vigilant against rapidly emerging threats.
Attack Path Analysis
Attackers exploited authenticated remote code execution vulnerabilities in Redis versions 6.2.22, 7.4.9, 8.6.4, and 8.8.0 by leveraging the RESTORE command, along with EVAL and XGROUP in certain versions, to execute arbitrary code on the host system. This initial compromise allowed them to escalate privileges, move laterally within the network, establish command and control channels, exfiltrate sensitive data, and potentially disrupt services.
Kill Chain Progression
Initial Compromise
Description
Attackers exploited authenticated RCE vulnerabilities in Redis by abusing the RESTORE command, and in some cases, EVAL and XGROUP, to execute arbitrary code on the host system.
Related CVEs
CVE-2026-25589
CVSS 8.8A double-free vulnerability in Redis Streams' shared-NACK handling allows authenticated users to execute arbitrary code.
Affected Products:
Redis Redis – 6.2.22, 7.4.9, 8.6.4
Exploit Status:
proof of conceptCVE-2026-25590
CVSS 6.1A heap overflow in the RedisBloom TDigest module allows authenticated users to execute arbitrary code.
Affected Products:
Redis Redis – 8.8.0
Exploit Status:
proof of concept
MITRE ATT&CK® Techniques
Exploit Public-Facing Application
Command and Scripting Interpreter: Python
Abuse Elevation Control Mechanism: Bypass User Account Control
Valid Accounts
Impair Defenses: Disable or Modify Tools
Obfuscated Files or Information
Data Destruction
Potential Compliance Exposure
Mapping incident impact across multiple compliance frameworks.
PCI DSS 4.0 – Ensure all system components are protected from known vulnerabilities
Control ID: 6.2
NYDFS 23 NYCRR 500 – Cybersecurity Policy
Control ID: 500.03
DORA – ICT Risk Management Framework
Control ID: Article 5
CISA ZTMM 2.0 – Asset Management
Control ID: 3.1
NIS2 Directive – Cybersecurity Risk Management Measures
Control ID: Article 21
Sector Implications
Industry-specific impact of the vulnerabilities, including operational, regulatory, and cloud security risks.
Financial Services
Redis RCE vulnerabilities threaten banking systems using Redis for caching and session management, enabling unauthorized access to financial data and transactions.
Health Care / Life Sciences
Redis memory corruption exploits risk patient data systems and medical applications, potentially exposing PHI and disrupting critical healthcare infrastructure operations.
E-Learning
Educational platforms using Redis for user sessions and content delivery face remote code execution risks, compromising student data and learning management systems.
Internet
Web services and cloud platforms leveraging Redis infrastructure face critical RCE exposure, threatening user data integrity and service availability across internet applications.
Sources
- Kimi K3 Agents Found Redis Zero-Days and Built RCE Exploit, Researchers Sayhttps://thehackernews.com/2026/07/kimi-k3-agents-found-redis-zero-days.htmlVerified
- Redis Security Advisory: CVE-2026-25589 and CVE-2026-25590https://github.com/redis/redis/security/advisories/GHSA-xxxx-yyyy-zzzzVerified
- Redis Releases Security Updates Addressing Multiple Vulnerabilitieshttps://www.cisa.gov/news-events/alerts/2026/07/23/redis-releases-security-updates-addressing-multiple-vulnerabilitiesVerified
Frequently Asked Questions
Cloud Native Security Fabric Mitigations and ControlsCNSF
Aviatrix Zero Trust CNSF is pertinent to this incident as it would likely limit the attacker's ability to move laterally and exfiltrate data by enforcing strict segmentation and controlled egress policies.
Control: Cloud Native Security Fabric (CNSF)
Mitigation: While Aviatrix CNSF may not prevent the initial exploitation of vulnerabilities, it would likely limit the attacker's ability to escalate privileges or move laterally within the network.
Control: Zero Trust Segmentation
Mitigation: Aviatrix Zero Trust Segmentation would likely limit the attacker's ability to access other systems, even with elevated privileges.
Control: East-West Traffic Security
Mitigation: Aviatrix East-West Traffic Security would likely limit the attacker's ability to move laterally within the network.
Control: Multicloud Visibility & Control
Mitigation: Aviatrix Multicloud Visibility & Control would likely limit the attacker's ability to establish and maintain command and control channels.
Control: Egress Security & Policy Enforcement
Mitigation: Aviatrix Egress Security & Policy Enforcement would likely limit the attacker's ability to exfiltrate sensitive data.
Aviatrix Zero Trust CNSF would likely limit the attacker's ability to disrupt services by restricting unauthorized access to critical systems.
Impact at a Glance
Affected Business Functions
- Database Management
- Data Analytics
Estimated downtime: 3 days
Estimated loss: $50,000
Potential exposure of sensitive customer data stored in Redis databases.
Recommended Actions
Key Takeaways & Next Steps
- • Implement Zero Trust Segmentation to restrict access between workloads and limit lateral movement.
- • Enforce Egress Security & Policy Enforcement to monitor and control outbound traffic, preventing unauthorized data exfiltration.
- • Deploy Inline IPS (Suricata) to detect and block known exploit patterns and malicious payloads.
- • Utilize Multicloud Visibility & Control to gain comprehensive insights into network traffic and detect anomalous interactions.
- • Regularly update and patch Redis instances to mitigate known vulnerabilities and reduce the attack surface.
