CVE-2026-56684

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% 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
Trending — Patch released this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

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.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

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_pr

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 Patch Available

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(3)

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 / EcosystemFixed in / PatchReleasedSource
ubuntuvalkey-tools (9.0.4-0ubuntu0.2) @ resolute2026-09-18ubuntu
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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
valkey8.1.1+dfsg1-3 ... 9.1.1-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
valkey8.1.1+dfsg1-3, 8.1.4+dfsg1-1, 8.1.4+dfsg1-29.1.1-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 27× in last 7d / 72× 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-09-18 20:09 UTCEG score recompute
  2. 2026-09-18 20:09 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 12:42 UTCVendor advisory
  5. 2026-09-18 00:15 UTCEG score recompute
  6. 2026-09-18 00:15 UTCVendor advisory
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-17 11:43 UTCVendor advisory
  9. 2026-09-16 22:58 UTCEG score recompute
  10. 2026-09-16 22:58 UTCVendor advisory
  11. 2026-09-16 14:08 UTCEPSS rescore
  12. 2026-09-16 10:30 UTCEG score recompute
  13. 2026-09-16 10:30 UTCVendor advisory
  14. 2026-09-16 05:15 UTCEPSS rescore
  15. 2026-09-15 22:07 UTCVendor advisory
  16. 2026-09-15 09:44 UTCEG score recompute
  17. 2026-09-15 09:44 UTCVendor advisory
  18. 2026-09-15 03:11 UTCEPSS rescore
  19. 2026-09-14 21:21 UTCVendor advisory
  20. 2026-09-14 08:34 UTCVendor advisory
  21. 2026-09-13 20:12 UTCEG score recompute
  22. 2026-09-13 20:12 UTCVendor advisory
  23. 2026-09-13 16:47 UTCEPSS rescore
  24. 2026-09-13 07:49 UTCVendor advisory
  25. 2026-09-12 19:27 UTCEG score recompute
Show 54 more
  1. 2026-09-12 19:27 UTCVendor advisory
  2. 2026-09-12 07:04 UTCVendor advisory
  3. 2026-09-11 18:42 UTCEG score recompute
  4. 2026-09-11 18:42 UTCVendor advisory
  5. 2026-09-11 14:53 UTCEPSS rescore
  6. 2026-09-11 06:19 UTCVendor advisory
  7. 2026-09-10 17:57 UTCEG score recompute
  8. 2026-09-10 17:57 UTCVendor advisory
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-10 05:35 UTCVendor advisory
  11. 2026-09-09 17:12 UTCVendor advisory
  12. 2026-09-09 03:26 UTCEG score recompute
  13. 2026-09-09 03:26 UTCVendor advisory
  14. 2026-09-08 22:01 UTCEPSS rescore
  15. 2026-09-07 16:58 UTCEG score recompute
  16. 2026-09-07 16:01 UTCEPSS rescore
  17. 2026-09-06 14:32 UTCEG score recompute
  18. 2026-09-06 13:47 UTCEPSS rescore
  19. 2026-09-06 02:10 UTCEG score recompute
  20. 2026-09-05 01:24 UTCEG score recompute
  21. 2026-09-04 12:56 UTCEG score recompute
  22. 2026-09-04 05:07 UTCEPSS rescore
  23. 2026-09-02 22:38 UTCEG score recompute
  24. 2026-09-02 14:12 UTCEPSS rescore
  25. 2026-09-01 21:47 UTCEG score recompute
  26. 2026-09-01 13:54 UTCEPSS rescore
  27. 2026-09-01 09:25 UTCEG score recompute
  28. 2026-09-01 04:40 UTCEPSS rescore
  29. 2026-08-31 07:42 UTCEG score recompute
  30. 2026-08-30 19:17 UTCEPSS rescore
  31. 2026-08-30 06:53 UTCEG score recompute
  32. 2026-08-30 01:22 UTCEPSS rescore
  33. 2026-08-29 03:58 UTCEG score recompute
  34. 2026-08-28 21:42 UTCEPSS rescore
  35. 2026-08-27 22:41 UTCEG score recompute
  36. 2026-08-27 14:25 UTCEPSS rescore
  37. 2026-08-26 21:57 UTCEG score recompute
  38. 2026-08-26 14:46 UTCEPSS rescore
  39. 2026-08-25 21:10 UTCEG score recompute
  40. 2026-08-25 13:49 UTCEPSS rescore
  41. 2026-08-24 20:24 UTCEG score recompute
  42. 2026-08-23 07:17 UTCEG score recompute
  43. 2026-08-23 00:19 UTCEPSS rescore
  44. 2026-08-22 06:33 UTCEG score recompute
  45. 2026-08-21 23:49 UTCEPSS rescore
  46. 2026-08-21 05:49 UTCEG score recompute
  47. 2026-08-20 22:55 UTCEPSS rescore
  48. 2026-08-20 05:05 UTCEG score recompute
  49. 2026-08-19 17:04 UTCEPSS rescore
  50. 2026-08-19 04:20 UTCEG score recompute
  51. 2026-08-19 04:11 UTCEG score recompute
  52. 2026-08-18 15:19 UTCEG score recompute
  53. 2026-08-18 14:32 UTCEG score recompute
  54. 2026-08-18 14:29 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-56684?
CVE-2026-56684 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 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 CVE-2026-56684 disclosed?
CVE-2026-56684 was first published in the National Vulnerability Database on August 18, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56684 actively exploited?
CVE-2026-56684 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 56.6% of all scored CVEs.
What is the CVSS score of CVE-2026-56684?
CVE-2026-56684 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-56684?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56684, 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

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.

Start Free Scan →Browse All CVEs