CVE-2026-86227

LOWPre-NVD 3.13.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-72176 (ENISA EUVD) · GHSA-74wm-q835-hxf9 (GitHub Security Advisories)Source: ENISA EUVD

3.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 3.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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."

CVSS v3
3.1
EG Score
3.1LOWmedium confidence
EG Risk
30
EG Risk 30/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity31% × 45%
Impact severity (EG Severity): CVSS 3.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (3.1): severity, escalated by confirmed exploitation. This CVE's 3.1 is its impact severity (EG Severity), not escalated.

EG Severity
3.1 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 6, 2026

Last Modified

September 9, 2026

References (9)

Vendor Advisories for CVE-2026-86227(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatvalkey-main-9.0.6-0.1.hum12026-09-01redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
valkey8.1.1+dfsg1-3 ... 9.1.1-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
valkey8.1.1+dfsg1-3, 8.1.4+dfsg1-1, 8.1.4+dfsg1-2, 9.1.1-1
  • every version up to 9.1.2-1: fixed in 9.1.2-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 100 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 2 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  6. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-10-29 17:43 UTCEG score recompute
  14. 2026-10-29 17:43 UTCVendor advisory
  15. 2026-10-29 17:43 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  16. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-27 04:55 UTCOSV refresh
  20. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  22. 2026-10-25 13:55 UTCEG score recompute
  23. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 73 more
  1. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-18 03:05 UTCEG score recompute
  6. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  12. 2026-10-12 14:51 UTCEG score recompute
  13. 2026-10-11 19:17 UTCEG score recompute
  14. 2026-10-11 16:34 UTCEG score recompute
  15. 2026-10-11 13:51 UTCEG score recompute
  16. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  19. 2026-10-09 01:58 UTCEG score recompute
  20. 2026-10-09 01:58 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  21. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-06 03:20 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  25. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  26. 2026-10-06 03:19 UTCEG score recompute
  27. 2026-10-06 03:19 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  28. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-10-03 04:33 UTCEG score recompute
  31. 2026-10-03 04:33 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  32. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-09-30 05:55 UTCEG score recompute
  36. 2026-09-30 05:55 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  37. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  39. 2026-09-27 07:17 UTCEG score recompute
  40. 2026-09-27 07:17 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  41. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  42. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-09-24 08:39 UTCEG score recompute
  44. 2026-09-24 08:39 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  45. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  47. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  48. 2026-09-21 10:01 UTCEG score recompute
  49. 2026-09-21 10:01 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  50. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  51. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  52. 2026-09-18 11:24 UTCEG score recompute
  53. 2026-09-18 11:24 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  54. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  55. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  56. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-09-15 12:46 UTCEG score recompute
  58. 2026-09-15 12:46 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  59. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-09-12 14:09 UTCEG score recompute
  61. 2026-09-12 14:09 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  62. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-09-09 15:32 UTCEG score recompute
  64. 2026-09-09 15:31 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  65. 2026-09-09 15:26 UTCNVD updateCVSS v4 → 1.3
  66. 2026-09-09 14:21 UTCEG score recompute
  67. 2026-09-09 14:21 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  68. 2026-09-09 14:20 UTCMITRE cvelistV5CVSS v4 → 2.3
  69. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  70. 2026-09-08 14:08 UTCEG score recompute
  71. 2026-09-08 14:07 UTCGHSA enrichmentGHSA-74wm-q835-hxf9 · GitHub severity LOW · GitHub CVSS 3.1
  72. 2026-09-06 23:33 UTCEG score recompute
  73. 2026-09-06 23:32 UTCNVD updateCVSS v4 → 1.3

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-86227?
CVE-2026-86227 is a low-severity vulnerability; its CVE record was published on September 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…
When was the CVE record for CVE-2026-86227 published?
The CVE record for CVE-2026-86227 was published on September 6, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-86227 actively exploited?
CVE-2026-86227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86227?
CVE-2026-86227 has a CVSS base score of 3.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86227?
A fix for CVE-2026-86227 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86227 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-86227

Explore →

Is Your Infrastructure Affected by CVE-2026-86227?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs