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."
CVE-2026-86227
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-09-07. a secondary CVSS source baseline 3.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(high)
- EG Risk
- 30(Track)EG Risk 30/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity31% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 42%
- KEV
- Not listed
Published
September 6, 2026
Last Modified
September 9, 2026
References (9)
- cna@vuldbhttps://github.com/user-attachments/files/30195539/RDB.zip
- cna@vuldbhttps://github.com/valkey-io/valkey/
- cna@vuldbhttps://github.com/valkey-io/valkey/commit/4691888e7fab3df128f0bde5750c9fde2ae552fa
- cna@vuldbhttps://github.com/valkey-io/valkey/issues/4222
- cna@vuldbhttps://github.com/valkey-io/valkey/pull/4229
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-86227
- cna@vuldbhttps://vuldb.com/submit/897659
- cna@vuldbhttps://vuldb.com/vuln/399380
- cna@vuldbhttps://vuldb.com/vuln/399380/cti
Vendor Advisories for CVE-2026-86227(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(2 across 2 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| valkey | 8.1.1+dfsg1-3 ... 9.1.1-1 (6 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| valkey | 8.1.1+dfsg1-3, 8.1.4+dfsg1-1, 8.1.4+dfsg1-2, 9.1.1-1 | — | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 36× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-24 08:39 UTCEG score recompute
- 2026-09-24 08:39 UTCGHSA enrichment
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 16:01 UTCEPSS rescore
- 2026-09-21 21:09 UTCEPSS rescore
- 2026-09-21 10:01 UTCEG score recompute
- 2026-09-21 10:01 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 11:24 UTCEG score recompute
- 2026-09-18 11:24 UTCGHSA enrichment
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 12:46 UTCEG score recompute
- 2026-09-15 12:46 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-12 14:09 UTCEG score recompute
- 2026-09-12 14:09 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-09 15:32 UTCEG score recompute
- 2026-09-09 15:31 UTCGHSA enrichment
Show 11 moreShow fewer
- 2026-09-09 15:26 UTCNVD updateCVSS v4 → 1.3
- 2026-09-09 14:21 UTCEG score recompute
- 2026-09-09 14:21 UTCGHSA enrichment
- 2026-09-09 14:20 UTCMITRE cvelistV5CVSS v4 → 2.3
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 14:08 UTCEG score recompute
- 2026-09-08 14:07 UTCGHSA enrichment
- 2026-09-06 23:33 UTCEG score recompute
- 2026-09-06 23:32 UTCNVD updateCVSS v4 → 1.3
- 2026-09-06 22:23 UTCEG score recompute
- 2026-09-06 22:23 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownDebian:13:valkey
Frequently asked(5)
What is CVE-2026-86227?
When was CVE-2026-86227 disclosed?
Is CVE-2026-86227 actively exploited?
What is the CVSS score of CVE-2026-86227?
How do I remediate CVE-2026-86227?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-86227
Is Your Infrastructure Affected by CVE-2026-86227?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.