A vulnerability was determined in valkey-io valkey 9.1.0. Impacted is the function moduleTimerHandler of the file src/module.c of the component Module Timer Subsystem. This manipulation causes double free. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized. Patch name: b349fe2821e3998534b1454c1b64a478daf8c6b7. To fix this issue, it is recommended to deploy a patch.
CVE-2026-82677
Score 2.4 from GitHub Security Advisory (severity: LOW) published 2026-08-31. a secondary CVSS source baseline 2.4; 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
- 2.4
- EG Score
- 2.4(high)
- EG Risk
- 27(Track)EG Risk 27/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 computedSeverity24% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 22%
- KEV
- Not listed
Published
August 31, 2026
Last Modified
August 31, 2026
References (11)
- cna@vuldbhttps://github.com/user-attachments/files/30118801/PoC.zip
- cna@vuldbhttps://github.com/valkey-io/valkey/
- cna@vuldbhttps://github.com/valkey-io/valkey/commit/b349fe2821e3998534b1454c1b64a478daf8c6b7
- cna@vuldbhttps://github.com/valkey-io/valkey/issues/4200
- cna@vuldbhttps://github.com/valkey-io/valkey/pull/4211
- cna@vuldbhttps://vuldb.com/cve/CVE-2026-82677
- cna@vuldbhttps://vuldb.com/submit/893959
- cna@vuldbhttps://vuldb.com/vuln/397172
- cna@vuldbhttps://vuldb.com/vuln/397172/cti
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/valkey-io/valkey/issues/4200
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://vuldb.com/submit/893959
Vendor Advisories for CVE-2026-82677(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 11× in last 7d / 37× 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-20 01:50 UTCEG score recompute
- 2026-09-20 01:50 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 08:00 UTCEG score recompute
- 2026-09-17 08:00 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 14:10 UTCEG score recompute
- 2026-09-14 14:10 UTCGHSA enrichment
- 2026-09-11 20:21 UTCEG score recompute
- 2026-09-11 20:21 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-09 02:31 UTCEG score recompute
- 2026-09-09 02:31 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 08:41 UTCEG score recompute
- 2026-09-06 08:41 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 14:52 UTCEG score recompute
- 2026-09-03 14:52 UTCGHSA enrichment
Show 12 moreShow fewer
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-08-31 21:02 UTCGHSA enrichment
- 2026-08-31 16:23 UTCEG score recompute
- 2026-08-31 16:23 UTCGHSA enrichment
- 2026-08-31 16:20 UTCNVD updateCVSS v4 → 1.9
- 2026-08-31 15:27 UTCEG score recompute
- 2026-08-31 15:27 UTCGHSA enrichment
- 2026-08-31 15:24 UTCMITRE cvelistV5CVSS v4 → 4.8
- 2026-08-31 10:17 UTCEG score recompute
- 2026-08-31 10:17 UTCNVD updateCVSS v4 → 1.9
- 2026-08-31 10:15 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-119
- CVE-2003-0819EG 10.0EPSS p99HIGH
- CVE-2003-0903EG 10.0EPSS p98HIGH
- CVE-2003-1339EG 10.0EPSS p99HIGH
- CVE-2003-0095EG 10.0EPSS p96HIGH
- CVE-2002-2227EG 10.0HIGH
- CVE-2002-2248EG 10.0EPSS p93HIGH
- CVE-2002-2250EG 10.0EPSS p94HIGH
- CVE-2002-2251EG 10.0EPSS p94HIGH
- CVE-2002-2253EG 10.0EPSS p94HIGH
- CVE-2002-2257EG 10.0EPSS p92HIGH
Frequently asked(5)
What is CVE-2026-82677?
When was CVE-2026-82677 disclosed?
Is CVE-2026-82677 actively exploited?
What is the CVSS score of CVE-2026-82677?
How do I remediate CVE-2026-82677?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82677
Is Your Infrastructure Affected by CVE-2026-82677?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.