CVE-2026-56684 Valkey: TLS pending-data processing use-after-free may allow remote code execution
An authenticated attacker can trigger a use-after-free in Valkey's TLS processing, potentially leading to remote code execution or server crashes.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-56684?
CVE-2026-56684 is a high-severity use after free vulnerability in valkey-io valkey, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Valkey is a distributed key-value database. Prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1, Valkey's tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.
Weakness: CWE-416
Which versions are affected by CVE-2026-56684?
1 open source package ship an affected version, including valkey.
| Package | Affected | Fixed in |
|---|---|---|
valkey Bitnami | All versions | 7.2.14, 8.0.10, 8.1.9, 9.0.5, 9.1.1 |
How do I fix CVE-2026-56684?
Upgrade valkey to a fixed version for your release line: 7.2.14, 8.0.10, 8.1.9 or 9.0.5.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is CVE-2026-56684 being exploited?
There is no known exploitation of CVE-2026-56684 in the wild and no public exploit code.
Sources
Also known as AZL-96888, BELL-CVE-2026-56684, BIT-valkey-2026-56684, DEBIAN-CVE-2026-56684, GHSA-53mc-f3m3-99vh, UBUNTU-CVE-2026-56684.