CVE-2026-56684: valkey · Use After Free
Affects valkeySource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in 9.1.1 : patch valkey soon.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 9.1.1, 9.0.5, 8.1.9 +2
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
| valkey-iovalkey | Affected
| Fixed in
|
GitHubvalkey-io/valkeypkg:github/valkey-io/valkeyOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Fixed versions are available: 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1. Users should upgrade to these versions or later to remediate the vulnerability. No vendor advisory content is provided to indicate alternative mitigations or that no action is required.
Description
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.
References
- github.com/valkey-io/valkey/security/advisories/GHSA-53mc-f3m3-99vh (opens in a new tab)
- github.com/valkey-io/valkey/pull/4234 (opens in a new tab)
- github.com/valkey-io/valkey/commit/7cd5bcb7575d750ec2de618db80da58680a10fe3 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/7.2.14 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/8.0.10 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/8.1.9 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/9.0.5 (opens in a new tab)
- github.com/valkey-io/valkey/releases/tag/9.1.1 (opens in a new tab)