CVE-2026-85522

A vulnerability has been identified in valkey-io valkey up to 9.0.5/9.1.1, involving an out-of-bounds read in the kvstoreGetHashtable function of src/kvstore.c via manipulation of the didx argument. The attack can be initiated remotely but requires cluster mode and attacker-controlled dump.rdb at startup, making exploitation difficult. The exploit has been made public, and a patch is available.

A vulnerability was determined in valkey-io valkey 9.1.0. The function moduleTimerHandler in src/module.c of the Module Timer Subsystem causes double free. The attack can be initiated remotely, and the exploit is public. A patch is available.

A security flaw was discovered in valkey-io valkey 9.1.0. The function handleClientsBlockedOnKey in src/blocked.c of the Blocked-on-keys Subsystem is vulnerable to use after free. The attack may be performed remotely but is difficult to exploit due to high complexity. The exploit is public, and a patch is available.

Use-after-free vulnerability in Valkey prior to versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1. The RESTORE command accepts a malformed RDB stream that assigns one NACK to multiple consumers, potentially allowing remote code execution.

Valkey, a distributed key-value database, contains a use-after-free vulnerability in the tlsProcessPendingData function. An authenticated client can trigger CLIENT KILL, causing deletion of a node from the list and potentially leading to server crash or remote code execution when TLS is enabled. The issue is fixed in versions 7.2.14, 8.0.10, 8.1.9, 9.0.5, and 9.1.1.

A vulnerability in Valkey from version 9.0.0 to 9.0.2 allows an attacker with network access to crash the server by sending a specially crafted request. The issue is caused by improper reset of networking state after processing an empty request, leading to an assertion failure and system abort.

A vulnerability in Valkey allows an attacker with access to the clusterbus port to send a malformed packet, potentially causing an out-of-bounds read and system crash. The issue stems from missing validation of the ping extension packet location within the buffer.

A vulnerability in Valkey allows a malicious user to inject arbitrary information into the client response stream via Lua scripts. The issue stems from improper handling of null characters in the Lua script error handling code, potentially corrupting or tampering with data for other users on the same connection.