CVE-2026-63639

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9%, top 44% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

August 18, 2026

Last Modified

August 20, 2026

Advisory Details (10)

Auto-updated Aug 18, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

8.1.9

Patch available: valkey-io/valkey 8.1.9

https://github.com/valkey-io/valkey/releases/tag/8.1.9
github_release Patch Available

8.0.10

Patch available: valkey-io/valkey 8.0.10

https://github.com/valkey-io/valkey/releases/tag/8.0.10
github_release Patch Available

7.2.14

Patch available: valkey-io/valkey 7.2.14

https://github.com/valkey-io/valkey/releases/tag/7.2.14
github_commit Patch Available

commit f8d2027e8d4d (valkey-io/valkey)

Patch available: valkey-io/valkey 8.0.10 (contains commit f8d2027e8d4d)

https://github.com/valkey-io/valkey/commit/f8d2027e8d4df790ac04974bf606408c8ea62778
github_commit Patch Available

commit e95911d4d65b (valkey-io/valkey)

Patch available: valkey-io/valkey 7.2.14 (contains commit e95911d4d65b)

https://github.com/valkey-io/valkey/commit/e95911d4d65be8789fa3705f44d7ed1e65378445
github_commit Patch Available

commit 98465eaffe3f (valkey-io/valkey)

Patch available: valkey-io/valkey 8.1.9 (contains commit 98465eaffe3f)

https://github.com/valkey-io/valkey/commit/98465eaffe3f95524a5046318bfbc4bdb9798291
github_commit Patch Available

commit 509cb3c74e8c (valkey-io/valkey)

Patch available: valkey-io/valkey 9.1.1 (contains commit 509cb3c74e8c)

https://github.com/valkey-io/valkey/commit/509cb3c74e8cbc9c0498ebe8b6c93dcd605e7271
github_commit Patch Available

commit 06bc7768fe60 (valkey-io/valkey)

Patch available: valkey-io/valkey 9.0.5 (contains commit 06bc7768fe60)

https://github.com/valkey-io/valkey/commit/06bc7768fe609f2054e69ccedefe7628f5675da9
github_pr

Reject corrupt stream RDB with shared NACK across consumers (CVE-2026-63639)

Fix merged in valkey-io/valkey PR #4073 on 2026-06-30 — awaiting tagged release

https://github.com/valkey-io/valkey/pull/4073
github Patch Available

UAF in stream deserialization may lead to remote code execution · Advisory · valkey-io/valkey · GitHub

https://github.com/valkey-io/valkey/security/advisories/GHSA-mvcj-73cw-22m4

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 03:58 UTCEG score recompute
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-27 15:59 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 03:13 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 01:53 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-25 00:36 UTCEG score recompute
  11. 2026-08-24 11:55 UTCEG score recompute
  12. 2026-08-23 10:34 UTCEG score recompute
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-22 09:16 UTCEG score recompute
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 07:58 UTCEG score recompute
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 19:19 UTCEG score recompute
  19. 2026-08-20 18:52 UTCEG score recompute
  20. 2026-08-19 18:15 UTCEG score recompute
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-19 04:20 UTCEG score recompute
  23. 2026-08-18 15:19 UTCEG score recompute
  24. 2026-08-18 14:32 UTCEG score recompute
  25. 2026-08-18 14:29 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-63639?
CVE-2026-63639 is a high vulnerability published on August 18, 2026. 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…
When was CVE-2026-63639 disclosed?
CVE-2026-63639 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63639 actively exploited?
CVE-2026-63639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 43.7% of all scored CVEs.
What is the CVSS score of CVE-2026-63639?
CVE-2026-63639 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-63639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63639, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63639

Explore →

Is Your Infrastructure Affected by CVE-2026-63639?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs