Servers and applications
GHSA-jcj7-v34w-v9vv
Use-after-free in the RDMA pending-data handler when a client
- Severity
- High 7.5
- Published
- 31 Aug 2026
- Last changed
- 31 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 8.0.11
- Weakness
- Use after free (CWE-416)
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H- Sources
- Project advisories (GitHub)
Description
An authenticated user can run a command that frees another client's connection while the RDMA transport is processing pending data, leaving a dangling pointer that is dereferenced shortly after. This reliably crashes the server process, and the freed heap chunk can be reclaimed with attacker-influenced bytes.
This issue only affects servers built with RDMA support (USE_RDMA) and configured with an RDMA listener, which is off by default and requires RDMA-capable hardware. Builds without RDMA are not affected, and the RDMA transport does not exist before 8.0.
The RDMA pending-data handler walked its connection list with an iterator that caches the next entry. Running a client's read handler from inside that loop can process a command such as CLIENT KILL, which synchronously frees a different client's connection, invalidating the cached entry. Separately, closing an RDMA connection freed it without removing it from the pending list, so a stale entry also persisted into later passes.
Workarounds
If you do not need RDMA, build without USE_RDMA or do not configure an RDMA listener. Otherwise, you can mitigate this issue by using Valkey ACLs to restrict the CLIENT command, in particular CLIENT KILL.
Affected software
| Software | Affected versions |
|---|---|
ValkeyServers and applications · github:valkey-io/valkey |
|
About Valkey
NoSQL database management software forked from Redis
- Developers who used it in the past year
- 2.4%Stack Overflow Developer Survey 2025, 2025
- Docker Hub pulls
- 404,291,684Docker Hub, 15 Nov 2026
- GitHub stars
- 27,721GitHub, 15 Nov 2026
- Forks
- 1,535GitHub, 15 Nov 2026
- Latest release
- 9.1.3GitHub, 15 Nov 2026
- Released
- 26 Oct 2026GitHub
- License
- 3-clause BSD LicenseWikidata
- Written in
- CWikidata
- First released
- 28 Mar 2024Wikidata
- First published on GitHub
- 22 Mar 2024GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 9.1 | 9.1.3 | Until 19 May 2031 |
| 9.0 | 9.0.7 | Until 21 Oct 2028 |
| 8.1 | 8.1.11 | Until 31 Mar 2030 |
| 8.0 | 8.0.12 | Until 15 Sept 2027 |
| 7.2 | 7.2.15 | Until 16 Apr 2029 |
From endoflife.date.
Vulnerabilities in Valkey
- In our list
- 14
- Published in the last 12 months
- 9
- Critical, last 12 months
- 0
- High, last 12 months
- 9
- Known exploited
- 0
- CVE-2026-130822Use-after-free when client eviction frees the client whose command is still executingHigh 7.5 19 Nov 2026
- GHSA-f4q9-j22m-xqq9Integer truncation in Valkey cluster publish message construction causes a heap buffer overflowHigh 8.8 26 Oct 2026
- GHSA-fq2f-crmw-q97rUnauthenticated use-after-free of the Lua interpreter state in Valkey (script debugger command cache)High 8.8 31 Aug 2026
- CVE-2026-63639UAF in stream deserialization may lead to remote code executionHigh 8.8 22 Jul 2026
- CVE-2026-56684UAF in Valkey with TLS may lead to remote code executionHigh 7.5 22 Jul 2026
- CVE-2026-27623Valkey is a distributed key-value database. Starting in version 9.0.0 and prior to version 9.0.3, a malicious actor with network access to Valkey can cause the system to abort by triggering an assertion. When processing incoming requests, the Valkey system does not properly reset the networking state after processing an empty request. A malicious actor can then send a request that the server…High 7.5 23 Feb 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-jcj7-v34w-v9vv
- github.com https://github.com/valkey-io/valkey/security/advisories/GHSA-jcj7-v34w-v9vv