Skip to main content

Valkey CVE-2026-63639

| EUVDEUVD-2026-60823 HIGH
Use After Free (CWE-416)
2026-08-18 GitHub_M
8.8
CVSS 3.1 · Vendor: GitHub_M
Share

Severity by source

Vendor (GitHub_M) PRIMARY
8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI
8.8 HIGH

Network-reachable via RESTORE command; PR:L because Valkey authentication is required; AC:L since payload crafting is mechanically straightforward as documented by the vendor test.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE
HIGH
qualitative
Red Hat
8.8 HIGH
qualitative

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Source Code Evidence Fetched
Aug 18, 2026 - 15:25 vuln.today
Analysis Generated
Aug 18, 2026 - 15:25 vuln.today
Patch available
Aug 18, 2026 - 15:02 EUVD
CVE Published
Aug 18, 2026 - 14:23 cve.org
HIGH 8.8

DescriptionCVE.org

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.

AnalysisAI

Use-after-free in Valkey's RESTORE command allows a low-privileged remote attacker to potentially execute arbitrary code by supplying a crafted RDB stream payload that assigns a single Pending Entry List (PEL) NACK to multiple stream consumers. Valkey versions prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1 across all active release trains are affected. When one consumer referencing the shared NACK is deleted while another still holds a pointer to the same memory, a use-after-free condition occurs that can corrupt the allocator heap and enable remote code execution. No public exploit or CISA KEV listing exists at time of analysis, though the vendor's own fix PR includes a detailed reproducer test that substantially lowers the barrier to weaponization.

Technical ContextAI

Valkey (cpe:2.3:a:valkey-io:valkey) is an open-source, Redis-compatible distributed key-value store that serializes and deserializes database state using the RDB (Redis Database) binary format. The RESTORE command accepts an externally-supplied RDB blob and reconstructs in-memory objects from it, including stream consumer groups. Stream consumer groups maintain a Pending Entry List (PEL) - a radix tree of NACK structs that track unacknowledged messages. Each NACK struct contains a pointer back to exactly one owning consumer. The vulnerability (CWE-416: Use After Free) arises because the RDB deserialization path in rdb.c did not validate that a NACK was already assigned to a different consumer before assigning it again, allowing a malformed payload to create aliased pointers where two distinct consumer structs point to the same NACK. When the first consumer is subsequently freed (e.g., on consumer deletion), the NACK memory is released while the second consumer still holds a dangling pointer to it, corrupting heap metadata and enabling attacker-controlled memory writes.

RemediationAI

Upgrade to a fixed release: Valkey 7.2.14 (https://github.com/valkey-io/valkey/releases/tag/7.2.14), 8.0.10 (https://github.com/valkey-io/valkey/releases/tag/8.0.10), 8.1.9 (https://github.com/valkey-io/valkey/releases/tag/8.1.9), 9.0.5 (https://github.com/valkey-io/valkey/releases/tag/9.0.5), or 9.1.1 (https://github.com/valkey-io/valkey/releases/tag/9.1.1). If immediate patching is not feasible, restrict RESTORE command access via Valkey ACLs to prevent untrusted or low-privileged clients from invoking it (ACL SETUSER with the RESTORE command removed from the allowed command set); note this disables cross-instance data migration workflows that rely on DUMP/RESTORE. Additionally, placing the Valkey instance behind a network boundary that limits access to trusted internal clients reduces exposure at the cost of operational flexibility. Neither workaround eliminates the underlying memory corruption defect - upgrading remains the only definitive fix.

Vendor StatusVendor

SUSE

Severity: Important
Product Status
SUSE Linux Enterprise High Performance Computing 15 SP7 SUSE Linux Enterprise Module for Server Applications 15 SP7 SUSE Linux Enterprise Server 15 SP7 SUSE Linux Enterprise Server for SAP Applications 15 SP7 Fixed
SUSE Linux Enterprise Server 15 SP6-LTSS Fixed
SUSE Linux Enterprise Server 16.0 SUSE Linux Enterprise Server for SAP applications 16.0 Fixed
SUSE Linux Enterprise Server for SAP Applications 15 SP6 Fixed
openSUSE Leap 16.0 Fixed

Share

CVE-2026-63639 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy