Loading story…
Redis disclosed and fixed five vulnerabilities in Redis OSS/CE, including four high-severity issues and one medium-severity flaw, warning that several bugs could lead to remote code execution after authentication. The most serious issue, CVE-2026-23479, is a use-after-free in blocking-client code that can enable arbitrary OS command execution on the host running Redis; Redis said it affects versions beginning with 7.2.0 across multiple stable branches. The broader set of flaws also includes invalid memory access bugs in the RESTORE command, including module-specific cases involving RedisTimeSeries and RedisBloom, as well as a Lua use-after-free affecting certain replica configurations.
See real exploitation activity before you spend the cycle.
5 events from the most recent confirmed update back to the earliest known activity.
A public technical write-up became available describing CVE-2026-23479, which Team Xint Code, an autonomous AI bug-hunting tool, discovered in Redis blocking-client code.
CVE-2026-23479 was introduced by the interaction of two Redis commits made in 2023, creating an authenticated use-after-free vulnerability in blocking-client code.
Redis publicly disclosed and remediated five vulnerabilities affecting Redis OSS/CE, including four high-severity issues and one medium-severity flaw that could potentially lead to remote code execution after authentication. Redis said it had no evidence of exploitation at the time of disclosure and provided mitigation and detection guidance.
A public report described a multi-stage exploitation chain for CVE-2026-23479 requiring authenticated Redis access, including a heap address leak, triggering a use-after-free via client eviction and unblocked client handling, and reclaiming freed memory with a fake client structure. The write-up said attackers could abuse a writable .got.plt entry under partial RELRO to redirect strcasecmp to system, enabling Redis commands to execute in the host shell.
On 2026-05-05, Redis released patched versions addressing CVE-2026-23479 and other disclosed vulnerabilities, including Redis OSS/CE 6.2.22, 7.2.14, 7.4.9, 8.2.6, 8.4.3, and 8.6.3, with additional module updates for RedisTimeSeries and RedisBloom.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
4 references tracked. Mallory keeps watching after this page renders.
scworld.com
Open sourcethehackernews.com
Open sourceseclists.org
Open sourcecvereports.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Redis disclosed five vulnerabilities affecting Redis Cloud, Redis Software, and Redis OSS/CE that could allow authenticated attackers to achieve **remote code execution**, system compromise, data exfiltration, or service disruption. The issues tracked as `CVE-2026-23479`, `CVE-2026-25243`, `CVE-2026-25588`, `CVE-2026-25589`, and `CVE-2026-23631` include an invalid memory access flaw in the `RESTORE` command, a use-after-free bug in the unblock client flow, and a Lua use-after-free condition in certain replica configurations. Public advisories and downstream alerts described four of the bugs as high severity and one as medium severity, with multiple flaws capable of leading to arbitrary code execution. Redis said **Redis Cloud** deployments had already been patched and required no customer action, while self-managed users were told to upgrade to fixed releases across Redis OSS/CE, Redis Software, RedisTimeSeries, and RedisBloom. Government and national CERT notices echoed the vendor guidance and urged administrators to review the advisories and apply updates promptly. Redis also said it had **no evidence of active exploitation** at publication time, but recommended immediate patching and hardening measures such as restricting network exposure, enforcing strong authentication, keeping protected mode enabled where appropriate, and applying least-privilege access controls.
Jun 29, 2026
Redis developers patched several high-severity vulnerabilities that allow authenticated attackers to execute code on Redis servers and potentially take full control of the host. The most severe, **DarkReplica** (`CVE-2026-23631`), affects Redis's newer functions engine during replication: an attacker can use `SLAVEOF` to point a server at a malicious master, trigger loading of a crafted RDB file, and exploit a use-after-free condition when replication replaces the active Lua engine while a long-running Lua function later resumes. Researchers reported that the bug can be turned into heap leak and memory corruption primitives and ultimately used to redirect internal pointers to `libc` for command execution on the underlying system.
Jun 29, 2026
A critical security vulnerability, tracked as CVE-2025-49844, has been identified in Redis, an open-source, in-memory database widely used for caching and data storage. The flaw is rated with a CVSS score of 10.0, indicating maximum severity and potential for significant impact. This vulnerability arises from a use-after-free condition in the Lua scripting engine of Redis, which can be exploited by an authenticated user. By crafting a malicious Lua script, an attacker can manipulate the garbage collector within Redis, triggering the use-after-free bug. Successful exploitation of this flaw allows remote code execution on the affected Redis server, granting attackers the ability to run arbitrary code with the privileges of the Redis process. All Redis versions up to and including 8.2.1 are affected by this vulnerability, as they include the vulnerable Lua scripting functionality. The issue has been addressed in Redis version 8.2.2, which contains the necessary patch to remediate the flaw. As an immediate mitigation for organizations unable to upgrade, Redis administrators are advised to restrict the execution of Lua scripts by disabling the EVAL and EVALSHA commands through Access Control Lists (ACLs). The vulnerability requires authentication, but in environments where Redis is exposed to untrusted users or where credentials are weak, the risk of exploitation is heightened. Security advisories recommend prompt patching and review of user permissions to minimize exposure. The flaw was publicly disclosed in early October 2025, and security researchers have emphasized the critical nature of the bug due to its potential for remote exploitation. No specific products beyond Redis itself have been listed as affected, but any deployment using vulnerable versions is at risk. The vulnerability has been confirmed to be remotely exploitable, making it a high-priority issue for organizations relying on Redis for critical infrastructure. The security community has highlighted the importance of monitoring for suspicious Lua script activity as an additional detection measure. Redis users are urged to consult official advisories and update their systems as soon as possible to prevent compromise. The disclosure underscores the ongoing risks associated with embedded scripting engines in widely deployed software. Organizations should also review their network exposure and ensure Redis instances are not accessible from untrusted networks. The incident serves as a reminder of the importance of timely patch management and the need for defense-in-depth strategies in database deployments.
Jul 23, 2026