CVE-2026-63639
Use-after-free in Valkey RESTORE can lead to remote code execution via crafted RDB stream.
Is CVE-2026-63639 being exploited?
Not confirmed. CVE-2026-63639 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.89% probability of exploitation in the next 30 days.
How severe is CVE-2026-63639?
CVE-2026-63639 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63639?
Yes. A fix has been recorded for CVE-2026-63639. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63639 affect?
CVE-2026-63639 affects Valkey versions prior to 7.2.14, 8.0.10, 8.1.9, 9.0.5, 9.1.1 (RESTORE feature). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63639?
Upgrade Valkey to 7.2.14/8.0.10/8.1.9/9.0.5/9.1.1 and restrict RESTORE access to trusted networks.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attackers can send a malformed RESTORE RDB stream causing a use-after-free that may enable remote code execution on Valkey nodes.
Patch when possible
- affected< 7.2.14
- affected>= 8.0.0 and < 8.0.10
- affected>= 8.1.0 and < 8.1.9
- affected>= 9.0.0 and < 9.0.5
- affected>= 9.1.0 and < 9.1.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.