CVE-2026-63639: Valkey: UAF in stream deserialization may lead to remote code execution
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 RESTORE command accepts a malformed RDB stream payload that assigns one Pending Entry List NACK to multiple consumers during stream consumer-group deserialization, causing a use-after-free when one consumer is deleted while another still references the shared NACK and potentially allowing remote code execution. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 7.2.14 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.0.10 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 8.1.9 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.0.5 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 9.1.1
Event History
Frequently Asked Questions
Who is exposed to this issue?
Valkey instances before 7.2.14, 8.0.10, 8.1.9, 9.0.5, or 9.1.1 are affected if an attacker can issue the RESTORE command with a crafted RDB stream payload. Exploitation requires low-privileged access but no user interaction.
Which versions contain the fix?
Update to 7.2.14, 8.0.10, 8.1.9, 9.0.5, or 9.1.1, depending on the release line in use. These versions fix the stream consumer-group deserialization flaw.