Answer in brief
CVE-2026-86227 records a Unknown severity vulnerability in valkey-io valkey kvstore.c kvstoreGetHashtable out-of-bounds. The current sources do not mark it as known exploited. The current feed maps valkey-io/valkey (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps valkey-io/valkey (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| valkey-io/valkeygeneric | 9.0.0 || 9.0.1 || 9.0.2 || 9.0.3 || 9.0.4 || 9.0.5 || 9.1.0 || 9.1.1 | Not reported |
Published upstream
Sep 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 6, 2026
A weakness has been identified in valkey-io valkey up to 9.0.5/9.1.1. This affects the function kvstoreGetHashtable of the file src/kvstore.c. This manipulation of the argument didx causes out-of-bounds read. It is possible to initiate the attack remotely. The attack is considered to have high complexity. It is indicated that the exploitability is difficult. The exploit has been made available to the public and could be used for attacks. Patch name: 4691888e7fab3df128f0bde5750c9fde2ae552fa. To fix this issue, it is recommended to deploy a patch. Exploitation requires cluster mode plus attacker-controlled dump.rdb at startup (data-dir write access, replication feed, or a stored crafted RDB) - an attacker-position DoS at boot, not network pre-auth. The issue report was closed stating it "is worth fixing for the sake of memory safety… but I don't think it meets our bar for a security disclosure."
Quoted source text, attributed separately from HOL analysis.