CVE-2026-63639

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.2% (66th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.2%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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 (value × EchelonGraph’s weight)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation1.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
1.2%
EPSS %ILE
66th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

September 18, 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 pull request

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 advisoryMentions a patch (unverified)

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

Vendor Advisories for CVE-2026-63639(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuvalkey-tools (9.0.4-0ubuntu0.2) @ resolute2026-10-13ubuntu
redhatvalkey-0:8.0.11-1.el10_02026-09-17redhat
redhatvalkey-0:8.0.11-1.el10_22026-09-08redhat
redhatvalkey-0:8.0.10-1.el9_82026-09-08redhat
redhatvalkey-main-9.0.6-0.1.hum12026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 2 ecosystems)
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
redict7.3.0+ds-1 ... 7.3.6+ds-3 (16 versions)
  • every version on: no fix on record
—
valkey8.1.1+dfsg1-3, 8.1.4+dfsg1-1, 8.1.4+dfsg1-2
  • every version up to 9.1.1-1: fixed in 9.1.1-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
valkey8.1.1+dfsg1-3 ... 9.1.2-1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 13× in last 7d / 82× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 143 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  2. 2026-10-13 11:58 UTCEG score recompute
  3. 2026-10-13 11:58 UTCVendor advisory
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  5. 2026-10-12 15:49 UTCEG score recompute
  6. 2026-10-11 19:33 UTCEG score recompute
  7. 2026-10-11 16:48 UTCEG score recompute
  8. 2026-10-11 14:10 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  14. 2026-10-07 11:14 UTCVendor advisory
  15. 2026-10-06 21:41 UTCEG score recompute
  16. 2026-10-06 21:41 UTCVendor advisory
  17. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  18. 2026-10-06 08:24 UTCEG score recompute
  19. 2026-10-06 08:24 UTCVendor advisory
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  21. 2026-10-05 11:45 UTCEG score recompute
  22. 2026-10-05 11:45 UTCVendor advisory
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  24. 2026-10-04 21:43 UTCVendor advisory
  25. 2026-10-04 06:18 UTCVendor advisory
Show 75 more
  1. 2026-10-03 17:40 UTCEG score recompute
  2. 2026-10-03 17:40 UTCVendor advisory
  3. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  4. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  5. 2026-10-02 15:39 UTCVendor advisory
  6. 2026-10-02 01:29 UTCEG score recompute
  7. 2026-10-02 01:29 UTCVendor advisory
  8. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  9. 2026-10-01 11:13 UTCVendor advisory
  10. 2026-09-30 22:34 UTCEG score recompute
  11. 2026-09-30 22:34 UTCVendor advisory
  12. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  13. 2026-09-30 09:51 UTCEG score recompute
  14. 2026-09-30 09:51 UTCVendor advisory
  15. 2026-09-28 22:40 UTCEG score recompute
  16. 2026-09-28 22:40 UTCVendor advisory
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  18. 2026-09-28 09:58 UTCVendor advisory
  19. 2026-09-27 21:19 UTCEG score recompute
  20. 2026-09-27 21:19 UTCVendor advisory
  21. 2026-09-27 07:58 UTCEG score recompute
  22. 2026-09-27 07:58 UTCVendor advisory
  23. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  24. 2026-09-25 01:30 UTCEG score recompute
  25. 2026-09-25 01:30 UTCVendor advisory
  26. 2026-09-24 08:59 UTCVendor advisory
  27. 2026-09-23 20:20 UTCEG score recompute
  28. 2026-09-23 20:20 UTCVendor advisory
  29. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  30. 2026-09-23 04:28 UTCEG score recompute
  31. 2026-09-23 04:28 UTCVendor advisory
  32. 2026-09-22 15:49 UTCVendor advisory
  33. 2026-09-22 03:11 UTCEG score recompute
  34. 2026-09-22 03:11 UTCVendor advisory
  35. 2026-09-21 14:32 UTCVendor advisory
  36. 2026-09-21 01:48 UTCEG score recompute
  37. 2026-09-21 01:48 UTCVendor advisory
  38. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  39. 2026-09-20 12:39 UTCVendor advisory
  40. 2026-09-19 23:33 UTCEG score recompute
  41. 2026-09-19 23:33 UTCVendor advisory
  42. 2026-09-19 10:54 UTCVendor advisory
  43. 2026-09-18 20:09 UTCEG score recompute
  44. 2026-09-18 20:09 UTCVendor advisory
  45. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  46. 2026-09-18 10:29 UTCVendor advisory
  47. 2026-09-17 21:51 UTCEG score recompute
  48. 2026-09-17 21:51 UTCVendor advisory
  49. 2026-09-17 03:48 UTCVendor advisory
  50. 2026-09-16 15:09 UTCEG score recompute
  51. 2026-09-16 15:09 UTCVendor advisory
  52. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  53. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  54. 2026-09-16 01:31 UTCVendor advisory
  55. 2026-09-15 12:53 UTCEG score recompute
  56. 2026-09-15 12:53 UTCVendor advisory
  57. 2026-09-15 00:09 UTCVendor advisory
  58. 2026-09-14 11:30 UTCVendor advisory
  59. 2026-09-13 22:51 UTCEG score recompute
  60. 2026-09-13 22:51 UTCVendor advisory
  61. 2026-09-13 10:13 UTCVendor advisory
  62. 2026-09-12 21:34 UTCEG score recompute
  63. 2026-09-12 21:34 UTCVendor advisory
  64. 2026-09-12 08:55 UTCVendor advisory
  65. 2026-09-11 20:17 UTCEG score recompute
  66. 2026-09-11 20:17 UTCVendor advisory
  67. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  68. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  69. 2026-09-11 07:12 UTCVendor advisory
  70. 2026-09-10 18:33 UTCEG score recompute
  71. 2026-09-10 18:33 UTCVendor advisory
  72. 2026-09-10 05:51 UTCVendor advisory
  73. 2026-09-09 17:12 UTCVendor advisory
  74. 2026-09-09 03:26 UTCEG score recompute
  75. 2026-09-09 03:26 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Same vendor

5 shown

redhat:RHSA-2026:61884 · redhat:RHSA-2026:64796 · ubuntu:USN-8771-1

Frequently asked(5)

What is CVE-2026-63639?
CVE-2026-63639 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-63639 published?
The CVE record for CVE-2026-63639 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-63639 actively exploited?
CVE-2026-63639 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (66th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63639?
CVE-2026-63639 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63639?
A fix for CVE-2026-63639 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63639 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs