CVE-2026-63639: valkey · Use After Free
Affects valkeySource CVE Database V5
Not known to be exploited · CVSS 8.8 High · fixed in 9.1.1 : patch valkey soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.1.1, 9.0.5, 8.1.9 +2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
GitHubvalkey-io/valkeypkg:github/valkey-io/valkeyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in valkey versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1. Users should upgrade to one of these versions or later to remediate the issue. No additional mitigations are indicated by the vendor advisory.
Description
CVE-2026-63639 is a high-severity use-after-free vulnerability in the valkey distributed key-value database. It affects the RESTORE command prior to versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1. The flaw arises when a malformed RDB stream payload assigns a single Pending Entry List NACK to multiple consumers during stream consumer-group deserialization, leading to a use-after-free condition if one consumer is deleted while others still reference the shared NACK. This can potentially allow remote code execution. The issue is fixed in the specified patched versions.
References
- github.com/valkey-io/valkey/security/advisories/GHSA-mvcj-73cw-22m4 (opens in a new tab)
- github.com/valkey-io/valkey/pull/4073 (opens in a new tab)
- github.com/valkey-io/valkey/commit/06bc7768fe609f2054e69ccedefe7628f5675da9 (opens in a new tab)
- github.com/valkey-io/valkey/commit/509cb3c74e8cbc9c0498ebe8b6c93dcd605e7271 (opens in a new tab)
- github.com/valkey-io/valkey/commit/98465eaffe3f95524a5046318bfbc4bdb9798291 (opens in a new tab)
- github.com/valkey-io/valkey/commit/e95911d4d65be8789fa3705f44d7ed1e65378445 (opens in a new tab)
- github.com/valkey-io/valkey/commit/f8d2027e8d4df790ac04974bf606408c8ea62778 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/7.2.14 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/8.0.10 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/8.1.9 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/9.0.5 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/9.1.1 (opens in a new tab)