All vulnerabilities

Servers and applications

CVE-2026-130822

Use-after-free when client eviction frees the client whose command is still executing

Severity
High 7.5
Published
19 Nov 2026
Last changed
19 Nov 2026
Added to UpHeron
19 Nov 2026
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
Also known as
GHSA-3885-pq5f-788j
Sources
Project advisories (GitHub)

Description

This is a use-after-free (CWE-416). Any authenticated user who can write to a key that other clients are blocked on (for example with BLPOP, BLMPOP, BZPOPMIN or XREAD BLOCK) can trigger it on a server with client eviction enabled. The blocked clients do not have to belong to the attacker. The result is a reliable crash of the server process.

Servers with maxmemory-clients 0 (the default) are not affected.

After a command runs, processCommand() in src/server.c calls handleClientsBlockedOnKeys() to serve the clients blocked on keys the command made ready. unblockClientOnKey() in src/blocked.c points server.current_client at each blocked client and re-executes its command through processCommandAndResetClient(), and processCommand() starts by calling evictClients().

If the replies sent to blocked clients earlier in the same pass push client memory over maxmemory-clients, evictClients() can pick the client whose command made the key ready, which is still on the call stack.

From valkey-io/valkey's security advisory. Shortened; the full text is there.

Workarounds

You can mitigate this issue by setting maxmemory-clients to 0, which disables client eviction. If you do, make sure client-output-buffer-limit and maxmemory still bound client memory.

If client eviction is required, you can reduce exposure by using Valkey ACLs so that untrusted users cannot write to keys that other clients block on, and cannot run the blocking commands (BLPOP, BRPOP, BLMOVE, BRPOPLPUSH, BLMPOP, BZPOPMIN, BZPOPMAX, BZMPOP, and XREAD / XREADGROUP with BLOCK).

Workarounds as given by valkey-io/valkey's security advisory.

Affected software

SoftwareAffected versions
ValkeyServers and applications · github:valkey-io/valkey
  • Every version up to 7.2.15

About Valkey

NoSQL database management software forked from Redis

From Wikidata, CC0 1.0.
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

Release lines

ReleaseLatestSecurity fixes
9.19.1.3Until 19 May 2031
9.09.0.7Until 21 Oct 2028
8.18.1.11Until 31 Mar 2030
8.08.0.12Until 15 Sept 2027
7.27.2.15Until 16 Apr 2029

From endoflife.date.

References