Valkey 9.2.0 Reaches General Availability as a Coordinated Patch Fixes a Client-Eviction Use-After-Free Across Five Other Branches
Valkey shipped 9.2.0 and five security-only updates on the same day, fixing a client-eviction use-after-free tracked as CVE-2026-130822.
Editor's Note ·
- Correction:
- The article quotes the GHSA-3885-pq5f-788j advisory as saying the bug involves replies pushing client memory "over the threshold," "causing the system to evict the client," and that this "results in reliable server crashes" on "systems with maxmemory-clients 0 (default setting)" being unaffected. The advisory's actual wording is: "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... The result is a reliable crash of the server process. Servers with maxmemory-clients 0 (the default) are not affected." The substance is accurate, but the quoted phrasing paraphrases rather than reproduces the advisory verbatim.
- Correction:
- The article's "What We Don't Know" section states the advisory "does not name a reporter." This is incorrect: the advisory's Credits section states "The defect was found and fixed by https://github.com/nadav-levanoni (issue #5422, fix #5435)." The advisory does not state whether the discovery method was an AI-assisted audit or conventional testing, so that part of the article's framing stands, but the claim that no reporter is named is wrong.
Overview
Valkey 9.2.0, the first stable release of the project’s 9.2 series, became generally available on November 18, 2026, according to the Valkey GitHub release notes. The same day, the project shipped security-only updates for five older branches — 9.1.4, 9.0.8, 8.1.12, 8.0.13, and 7.2.16 — fixing a client-eviction use-after-free flaw tracked as CVE-2026-130822. Valkey, a Linux Foundation-hosted fork of Redis, had previously shipped a 9.2 release candidate in September carrying most of the features that are now final in 9.2.0.
What We Know
The vulnerability, cataloged as GHSA-3885-pq5f-788j, is rated High severity with a CVSS score of 7.5 and vector string CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. The advisory describes it as a bug in which “replies sent to blocked clients push client memory over the threshold, causing the system to evict the client whose command initiated the unblock operation while that client is still active on the call stack,” a condition the advisory says “results in reliable server crashes.” An authenticated user can trigger the crash by writing to a key while other clients are blocked on it, but only on servers that have client eviction enabled; the advisory notes that “systems with maxmemory-clients 0 (default setting) remain unaffected.”
The fix landed in six branches on the same day: the new 9.2.0 stable release itself, plus dedicated security updates 9.1.4, 9.0.8, 8.1.12, 8.0.13, and 7.2.16, according to the Valkey releases page. The 9.1.4 release notes and the 7.2.16 release notes both describe the change as a fix for “a use-after-free crash in client eviction when maxmemory-clients is enabled,” and both carry an “Upgrade urgency SECURITY” label — the project’s highest priority tier for a release.
Separate from the security fix, 9.2.0 is the first stable release to carry several features Valkey had been previewing since its release candidates, according to the Valkey blog. These include a Path Hash data type, a radix-tree structure described in the release notes as supporting “exact lookup, longest-prefix matching, and prefix traversal over binary-safe paths”; forkless RDB snapshots, which run background-thread snapshots and full synchronizations without the copy-on-write overhead of forking a process; Zstandard compression for RDB persistence and replication alongside the existing LZ4 option; named, reusable ACL roles that let administrators, in the blog’s words, “define a permission policy once and apply it to many users”; and server-side hot-key detection. The project’s blog reports that a B+ tree replacement for the large sorted-set encoding makes “large sorted sets use 36% to 43% less memory overhead per member,” and that LZ4 replication compression “cut replication bandwidth by 52% with less than 1% throughput overhead” in the project’s own testing.
The coordinated security release follows a rise in Valkey’s own disclosed advisory count earlier this year. A Valkey blog post published in September said the project “published five security advisories in Valkey’s first 21 months, from the March 2024 fork through the end of 2025,” compared with “seven advisories in the first eight months of 2026 and shipped almost three dozen security-adjacent fixes.” The post attributed the acceleration partly to the falling cost of automated code review, writing that “new AI models can search codebases for vulnerabilities cheaply, and the cost of generating reports is almost zero,” and said the project had begun “running AI-driven adversarial audits” against its own code that “has so far produced 34 real bugs” as of the post’s September date.
What We Don’t Know
The GHSA advisory for CVE-2026-130822 does not name a reporter or describe how the bug was found, so it is not established whether this particular fix originated from the AI-assisted review process the September blog post described or from conventional testing. Valkey’s own release notes and blog post do not state whether any production deployments were affected before the patch shipped.