Servers and applications
CVE-2026-63639
UAF in stream deserialization may lead to remote code execution
- Severity
- High 8.8
- Published
- 22 Jul 2026
- Last changed
- 22 Jul 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 7.2.14
- Exploit chance
- 0.9% in the next 30 daysHigher than 60% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Also known as
- GHSA-mvcj-73cw-22m4
- Sources
- Project advisories (GitHub)
Description
An authenticated user may use a specially crafted RESTORE command to inject a malformed RDB payload containing duplicate Pending Entry List (PEL) assignments. This triggers a use-after-free during stream consumer group deserialization or consumer deletion, potentially leading to remote code execution.
The problem exists in all versions of Valkey.
Workarounds
An additional workaround to mitigate the problem without patching the valkey-server executable is to prevent users from executing the RESTORE command. This can be done using ACLs to restrict access to the RESTORE command, or by disabling/renaming the command in your valkey.conf.
Affected software
| Software | Affected versions |
|---|---|
ValkeyServers and applications · github:valkey-io/valkey |
|
About Valkey
NoSQL database management software forked from Redis
- Developers who used it in the past year
- 2.4%Stack Overflow Developer Survey 2025, 2025
- Docker Hub pulls
- 404,291,684Docker Hub, 15 Nov 2026
- GitHub stars
- 27,721GitHub, 15 Nov 2026
- Forks
- 1,535GitHub, 15 Nov 2026
- Latest release
- 9.1.3GitHub, 15 Nov 2026
- Released
- 26 Oct 2026GitHub
- License
- 3-clause BSD LicenseWikidata
- Written in
- CWikidata
- First released
- 28 Mar 2024Wikidata
- First published on GitHub
- 22 Mar 2024GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 9.1 | 9.1.3 | Until 19 May 2031 |
| 9.0 | 9.0.7 | Until 21 Oct 2028 |
| 8.1 | 8.1.11 | Until 31 Mar 2030 |
| 8.0 | 8.0.12 | Until 15 Sept 2027 |
| 7.2 | 7.2.15 | Until 16 Apr 2029 |
From endoflife.date.
Vulnerabilities in Valkey
- In our list
- 14
- Published in the last 12 months
- 9
- Critical, last 12 months
- 0
- High, last 12 months
- 9
- Known exploited
- 0
- CVE-2026-130822Use-after-free when client eviction frees the client whose command is still executingHigh 7.5 19 Nov 2026
- GHSA-f4q9-j22m-xqq9Integer truncation in Valkey cluster publish message construction causes a heap buffer overflowHigh 8.8 26 Oct 2026
- GHSA-fq2f-crmw-q97rUnauthenticated use-after-free of the Lua interpreter state in Valkey (script debugger command cache)High 8.8 31 Aug 2026
- GHSA-jcj7-v34w-v9vvUse-after-free in the RDMA pending-data handler when a clientHigh 7.5 31 Aug 2026
- CVE-2026-56684UAF in Valkey with TLS may lead to remote code executionHigh 7.5 22 Jul 2026
- CVE-2026-27623Valkey is a distributed key-value database. Starting in version 9.0.0 and prior to version 9.0.3, a malicious actor with network access to Valkey can cause the system to abort by triggering an assertion. When processing incoming requests, the Valkey system does not properly reset the networking state after processing an empty request. A malicious actor can then send a request that the server…High 7.5 23 Feb 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-63639
- GitHub Advisory Database https://github.com/advisories/GHSA-mvcj-73cw-22m4
- github.com https://github.com/valkey-io/valkey/security/advisories/GHSA-mvcj-73cw-22m4