CVE-2026-82631

LOWPre-NVD 2.22.2—
EchelonGraph scoreHIGH confidence

Score 2.2 from GitHub Security Advisory (severity: LOW) published 2026-08-31. a secondary CVSS source baseline 2.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
2.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 2.2Exploit: Elevated riskExposed: 0

A fix is available — apply it.

A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexity level is associated with this attack. The exploitability is described as difficult. The exploit has been released to the public and may be used for attacks. The patch is identified as b2fb0e13f5b4c8c2fb63dcfc2c37a067a0d6d20b. Applying a patch is advised to resolve this issue.

CVSS v3
2.2
EG Score
2.2(high)
EG Risk
26(Track)
EG Risk 26/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 computed
Severity22% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

August 31, 2026

Last Modified

August 31, 2026

References (9)

Vendor Advisories for CVE-2026-82631(1)

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 / EcosystemFixed in / 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 rangeFixed inDependents
valkey8.1.1+dfsg1-3 ... 9.1.1-1 (6 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
valkey8.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.

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 12× in last 7d / 54× 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.

  1. 2026-09-24 14:04 UTCEPSS rescore
  2. 2026-09-23 17:54 UTCEPSS rescore
  3. 2026-09-22 19:06 UTCEG score recompute
  4. 2026-09-22 19:06 UTCVendor advisory
  5. 2026-09-22 19:06 UTCGHSA enrichment
  6. 2026-09-22 16:01 UTCEPSS rescore
  7. 2026-09-21 21:09 UTCEPSS rescore
  8. 2026-09-20 20:16 UTCEPSS rescore
  9. 2026-09-20 01:23 UTCEG score recompute
  10. 2026-09-20 01:23 UTCVendor advisory
  11. 2026-09-20 01:23 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-17 07:40 UTCEG score recompute
  14. 2026-09-17 07:40 UTCVendor advisory
  15. 2026-09-17 07:40 UTCGHSA enrichment
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-15 03:12 UTCEPSS rescore
  19. 2026-09-15 03:12 UTCEPSS rescore
  20. 2026-09-14 13:54 UTCEG score recompute
  21. 2026-09-14 13:54 UTCVendor advisory
  22. 2026-09-14 13:54 UTCGHSA enrichment
  23. 2026-09-11 20:11 UTCEG score recompute
  24. 2026-09-11 20:11 UTCVendor advisory
  25. 2026-09-11 20:11 UTCGHSA enrichment
Show 29 more
  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-09 02:24 UTCEG score recompute
  4. 2026-09-09 02:24 UTCVendor advisory
  5. 2026-09-09 02:23 UTCGHSA enrichment
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-06 13:48 UTCEPSS rescore
  8. 2026-09-06 08:34 UTCEG score recompute
  9. 2026-09-06 08:34 UTCGHSA enrichment
  10. 2026-09-05 15:31 UTCEPSS rescore
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-03 14:51 UTCEG score recompute
  13. 2026-09-03 14:51 UTCGHSA enrichment
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-09-01 04:40 UTCEPSS rescore
  18. 2026-08-31 21:02 UTCEG score recompute
  19. 2026-08-31 21:02 UTCGHSA enrichment
  20. 2026-08-31 12:27 UTCEG score recompute
  21. 2026-08-31 12:27 UTCGHSA enrichment
  22. 2026-08-31 12:20 UTCNVD updateCVSS v4 → 1.2
  23. 2026-08-31 11:40 UTCEG score recompute
  24. 2026-08-31 11:40 UTCGHSA enrichment
  25. 2026-08-31 11:39 UTCMITRE cvelistV5CVSS v4 → 2.1
  26. 2026-08-31 08:36 UTCEG score recompute
  27. 2026-08-31 08:34 UTCNVD updateCVSS v4 → 1.2
  28. 2026-08-31 07:53 UTCEG score recompute
  29. 2026-08-31 07:53 UTCMITRE cvelistV5first tracked

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

Frequently asked(5)

What is CVE-2026-82631?
CVE-2026-82631 is a low vulnerability published on August 31, 2026. A security flaw has been discovered in valkey-io valkey 9.1.0. The affected element is the function handleClientsBlockedOnKey of the file src/blocked.c of the component Blocked-on-keys Subsystem. The manipulation results in use after free. The attack may be performed from remote. A high complexity…
When was CVE-2026-82631 disclosed?
CVE-2026-82631 was first published in the National Vulnerability Database on August 31, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82631 actively exploited?
CVE-2026-82631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.2% of all scored CVEs.
What is the CVSS score of CVE-2026-82631?
CVE-2026-82631 has a CVSS v3 base score of 2.2 (NVD).
How do I remediate CVE-2026-82631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82631, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82631?

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

Book a Demo →Browse All CVEs