Skip to main content
Mallory
High

Redis unblock client flow use-after-free RCE

IdentifiersCVE-2026-23479CWE-416· Use After Free

CVE-2026-23479 is an authenticated use-after-free vulnerability in Redis affecting redis-server from 7.2.0 through vulnerable releases prior to the vendor fixes. The flaw is in the blocked-client re-execution path, specifically the unblock client flow in src/blocked.c, including unblockClientOnKey(). When Redis re-executes a blocked command, it calls processCommandAndResetClient() but does not correctly handle an error return indicating that the client was freed as a side effect. If the blocked client is evicted during this flow, Redis continues to use the stale client pointer, creating a use-after-free condition. Public reporting states the bug was introduced by the interaction of 2023 changes and remained present across stable branches until the May 2026 fixes. Technical write-ups describe exploitation by reclaiming the freed client allocation with attacker-controlled data so that Redis later processes a fake client structure, which can be leveraged to corrupt memory and ultimately achieve remote code execution.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can lead to remote code execution in the context of the redis-server process. Public exploit descriptions show that an attacker can turn the use-after-free into controlled memory corruption and redirect execution flow, resulting in arbitrary OS command execution on the host running Redis. Depending on deployment, this can enable full compromise of the Redis instance, access to in-memory data, further host-level post-exploitation, service disruption, and potential lateral movement from the affected server.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exploitability by restricting Redis network exposure to trusted sources only, keeping instances off the public internet, enforcing strong authentication, enabling protected mode where applicable, and tightening ACLs to least privilege. Deny high-risk capabilities used in published exploit chains where operationally feasible, especially CONFIG and Lua scripting/EVAL if not required. Use TLS for administrative access, rotate shared Redis credentials, and monitor for anomalous authenticated access, crashes, suspicious command execution, unusual ingress/egress, and unexpected filesystem changes.

Remediation

Patch, then assume compromise.

Upgrade Redis to a fixed release. The provided content states the issue is patched in Redis OSS/CE versions 7.2.14, 7.4.9, 8.2.6, 8.4.3, and 8.6.3; some Redis advisories also reference 6.2.22 as part of the broader May 2026 security release set. For Redis Software, apply the vendor-provided fixed builds referenced in the Redis advisory. Redis Cloud was reported as already patched. Prioritize upgrading any internet-exposed or broadly accessible authenticated Redis deployments.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
RedisRedisapplication
RedisRedis Softwareapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity42

Community discussion across Reddit, Mastodon, and other social sources.