CVE-2026-56684

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.9% (58th 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
7.5EG
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: 0.9%CVSS: 7.5Exploit: 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 tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a use-after-free that can crash the server or potentially allow remote code execution when TLS is enabled. This issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.9% × 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
0.9%
EPSS %ILE
58th
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 (8)

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

9.1.1

Patch available: valkey-io/valkey 9.1.1

https://github.com/valkey-io/valkey/releases/tag/9.1.1
GitHub release Patch Available

9.0.5

Patch available: valkey-io/valkey 9.0.5

https://github.com/valkey-io/valkey/releases/tag/9.0.5
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 7cd5bcb7575d (valkey-io/valkey)

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

https://github.com/valkey-io/valkey/commit/7cd5bcb7575d750ec2de618db80da58680a10fe3
GitHub pull request

Fix use-after-free in tlsProcessPendingData() on CLIENT KILL (CVE-2026-56684)

Fix merged in valkey-io/valkey PR #4234 on 2026-07-21 — awaiting tagged release

https://github.com/valkey-io/valkey/pull/4234
GitHub advisoryMentions a patch (unverified)

UAF in Valkey with TLS may lead to remote code execution · Advisory · valkey-io/valkey · GitHub

https://github.com/valkey-io/valkey/security/advisories/GHSA-53mc-f3m3-99vh

Vendor Advisories for CVE-2026-56684(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-07ubuntu
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 11× in last 7d / 88× 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 148 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 48 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 0.9% · 58th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-12 15:54 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:53 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  12. 2026-10-07 11:14 UTCVendor advisory
  13. 2026-10-06 21:40 UTCEG score recompute
  14. 2026-10-06 21:40 UTCVendor advisory
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  16. 2026-10-06 08:25 UTCEG score recompute
  17. 2026-10-06 08:25 UTCVendor advisory
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  19. 2026-10-05 11:45 UTCEG score recompute
  20. 2026-10-05 11:45 UTCVendor advisory
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-10-04 21:43 UTCVendor advisory
  23. 2026-10-04 06:02 UTCVendor advisory
  24. 2026-10-03 17:40 UTCEG score recompute
  25. 2026-10-03 17:40 UTCVendor advisory
Show 75 more
  1. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  2. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  3. 2026-10-02 15:39 UTCVendor advisory
  4. 2026-10-02 01:29 UTCEG score recompute
  5. 2026-10-02 01:29 UTCVendor advisory
  6. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  7. 2026-10-01 10:45 UTCVendor advisory
  8. 2026-09-30 22:13 UTCEG score recompute
  9. 2026-09-30 22:13 UTCVendor advisory
  10. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  11. 2026-09-30 09:51 UTCEG score recompute
  12. 2026-09-30 09:51 UTCVendor advisory
  13. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  14. 2026-09-28 22:04 UTCEG score recompute
  15. 2026-09-28 22:04 UTCVendor advisory
  16. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  17. 2026-09-28 09:41 UTCVendor advisory
  18. 2026-09-27 21:19 UTCEG score recompute
  19. 2026-09-27 21:19 UTCVendor advisory
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  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 0.9% · 57th percentile
  24. 2026-09-25 01:30 UTCEG score recompute
  25. 2026-09-25 01:30 UTCVendor advisory
  26. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  27. 2026-09-24 12:55 UTCVendor advisory
  28. 2026-09-24 00:32 UTCEG score recompute
  29. 2026-09-24 00:32 UTCVendor advisory
  30. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-09-23 12:10 UTCVendor advisory
  32. 2026-09-22 23:47 UTCEG score recompute
  33. 2026-09-22 23:47 UTCVendor advisory
  34. 2026-09-22 11:11 UTCVendor advisory
  35. 2026-09-21 22:48 UTCEG score recompute
  36. 2026-09-21 22:48 UTCVendor advisory
  37. 2026-09-21 10:26 UTCVendor advisory
  38. 2026-09-20 22:04 UTCEG score recompute
  39. 2026-09-20 22:04 UTCVendor advisory
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-09-20 09:41 UTCVendor advisory
  42. 2026-09-19 21:12 UTCEG score recompute
  43. 2026-09-19 21:12 UTCVendor advisory
  44. 2026-09-19 08:33 UTCVendor advisory
  45. 2026-09-18 20:09 UTCEG score recompute
  46. 2026-09-18 20:09 UTCVendor advisory
  47. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-09-18 12:42 UTCVendor advisory
  49. 2026-09-18 00:15 UTCEG score recompute
  50. 2026-09-18 00:15 UTCVendor advisory
  51. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-09-17 11:43 UTCVendor advisory
  53. 2026-09-16 22:58 UTCEG score recompute
  54. 2026-09-16 22:58 UTCVendor advisory
  55. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  56. 2026-09-16 10:30 UTCEG score recompute
  57. 2026-09-16 10:30 UTCVendor advisory
  58. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  59. 2026-09-15 22:07 UTCVendor advisory
  60. 2026-09-15 09:44 UTCEG score recompute
  61. 2026-09-15 09:44 UTCVendor advisory
  62. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  63. 2026-09-14 21:21 UTCVendor advisory
  64. 2026-09-14 08:34 UTCVendor advisory
  65. 2026-09-13 20:12 UTCEG score recompute
  66. 2026-09-13 20:12 UTCVendor advisory
  67. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  68. 2026-09-13 07:49 UTCVendor advisory
  69. 2026-09-12 19:27 UTCEG score recompute
  70. 2026-09-12 19:27 UTCVendor advisory
  71. 2026-09-12 07:04 UTCVendor advisory
  72. 2026-09-11 18:42 UTCEG score recompute
  73. 2026-09-11 18:42 UTCVendor advisory
  74. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  75. 2026-09-11 06:19 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-56684?
CVE-2026-56684 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 tlsProcessPendingData function iterates pending_list while an authenticated client can trigger CLIENT KILL, causing connTLSClose to delete the iterator's cached next node and producing a…
When was the CVE record for CVE-2026-56684 published?
The CVE record for CVE-2026-56684 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-56684 actively exploited?
CVE-2026-56684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56684?
CVE-2026-56684 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56684?
A fix for CVE-2026-56684 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-56684 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-56684

Explore →

Is Your Infrastructure Affected by CVE-2026-56684?

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

Book a Demo →Browse All CVEs