Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.
CVE-2026-66373
HIGHPre-NVD 7.57.5—Trending — 4 sources updated this weekElevated
EchelonGraph scoreHIGH confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-25. a secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(high)
- EG Risk
- 50(Track*)EG Risk 50/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 computedSeverity75% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 38%
- KEV
- Not listed
Published
July 25, 2026
Last Modified
July 28, 2026
Advisory Details (5)
Auto-updated Jul 25, 2026Patch available. Sources: github_pr.
generic
Chaofan Shou on X: "Kimi K3 exploited the latest Redis server with a 0day it discovered. All it took was 27min with 32 agents. https://t.co/ZOKA2wchLa https://t.co/0sIeYgfg65" / X
https://x.com/Fried_rice/status/2080059356322918777generic
Kimi K3 exploited the latest Redis server | Hacker News
https://news.ycombinator.com/item?id=49024938github_pr Patch Available
Reject corrupt stream RDB with shared NACK across consumers
Patch available: redis/redis 8.8-m03 (PR #15081 merged 2026-04-23)
https://github.com/redis/redis/pull/15081generic
Comparing 8.6.4...8.8.0 · redis/redis · GitHub
https://github.com/redis/redis/compare/8.6.4...8.8.0generic
GitHub - berabuddies/redis-poc: RCE PoC for Redis 6.2.22, 7.4.9, 8.6.4, 8.8.0 · GitHub
https://github.com/berabuddies/redis-pocVendor Advisories for CVE-2026-66373(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-66373Microsoft Security Response Center (MSRC)
Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free. NOTE: this issue exists because of an incomplete fix for CVE-2026-25243.
- GHSA-c964-568j-vxx7GitHub Security AdvisoriesHigh
Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE,...
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 19× in last 7d / 19× 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-07-28 05:37 UTCEG score recompute
- 2026-07-28 05:37 UTCGHSA enrichment
- 2026-07-28 04:36 UTCEG score recompute
- 2026-07-28 04:36 UTCGHSA enrichment
- 2026-07-28 03:10 UTCGHSA enrichment
- 2026-07-27 15:00 UTCEG score recompute
- 2026-07-27 15:00 UTCGHSA enrichment
- 2026-07-27 14:14 UTCEPSS rescore
- 2026-07-27 03:21 UTCGHSA enrichment
- 2026-07-26 15:07 UTCEG score recompute
- 2026-07-26 15:07 UTCGHSA enrichment
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 02:54 UTCEG score recompute
- 2026-07-26 02:54 UTCGHSA enrichment
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 14:18 UTCEPSS rescore
- 2026-07-25 00:57 UTCEG score recompute
- 2026-07-25 00:56 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-66373?
CVE-2026-66373 is a high vulnerability published on July 25, 2026. Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payload where the same NACK (pending entry) is referenced by more than one consumer, because deleting both consumers via XGROUP DELCONSUMER leads to a double free.…
When was CVE-2026-66373 disclosed?
CVE-2026-66373 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66373 actively exploited?
CVE-2026-66373 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.8% of all scored CVEs.
What is the CVSS score of CVE-2026-66373?
CVE-2026-66373 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-66373?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66373, 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
Explore the affected products and dependency analysis for CVE-2026-66373
Is Your Infrastructure Affected by CVE-2026-66373?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.