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 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.
References10
- github.com/valkey-io/valkey/commit/06bc7768fe609f2054e69ccedefe…
- github.com/valkey-io/valkey/commit/509cb3c74e8cbc9c0498ebe8b6c9…
- github.com/valkey-io/valkey/commit/98465eaffe3f95524a5046318bfb…
- github.com/valkey-io/valkey/commit/e95911d4d65be8789fa3705f44d7…
- github.com/valkey-io/valkey/commit/f8d2027e8d4df790ac04974bf606…
- github.com/valkey-io/valkey/pull/4073
- github.com/valkey-io/valkey/releases/tag/7.2.14
- github.com/valkey-io/valkey/releases/tag/8.0.10
- github.com/valkey-io/valkey/releases/tag/8.1.9
- github.com/valkey-io/valkey/releases/tag/9.0.5
Metrics
- CVSS 3.1
-
8.8
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 60 · as of 11 November 2026
- CWE
- CWE-416
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.