CVE-2026-66373

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

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, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-48762 (ENISA EUVD) · GHSA-c964-568j-vxx7 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.9%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
50
EG Risk 50/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.9%
EPSS %ILE
59th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.9% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 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, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

July 25, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Jul 25, 2026
Patch available. Sources: github_pr.
Web page

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/2080059356322918777
Web page

Kimi K3 exploited the latest Redis server | Hacker News

https://news.ycombinator.com/item?id=49024938
GitHub pull request 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/15081
Web page

Comparing 8.6.4...8.8.0 · redis/redis · GitHub

https://github.com/redis/redis/compare/8.6.4...8.8.0
Web page

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-poc

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatredis-0:6.2.7-1.el9_2.72026-09-22redhat
redhatredis-0:6.2.7-1.el9_4.72026-09-22redhat
redhatredis:7-9060020260917140656.92026-09-21redhat
redhatredis:7-9040020260917140622.92026-09-21redhat
redhatredis:6-8080020260916133522.63b345852026-09-21redhat
redhatredis:6-8060020260916133704.ad008a3a2026-09-21redhat
redhatredis:6-8040020260916133739.522a0ee42026-09-21redhat
redhatvalkey-0:8.0.11-1.el10_02026-09-17redhat
redhatredis-0:6.2.24-1.el9_62026-09-14redhat
redhatvalkey-0:8.0.10-1.el9_82026-09-08redhat
redhatvalkey-0:8.0.11-1.el10_22026-09-08redhat
redhatredis-0:6.2.24-1.el9_82026-09-08redhat
redhatredis:6-8100020260821173603.489197e62026-09-08redhat
redhatredis:7-9080020260821173335.92026-09-08redhat
redhatvalkey-main-9.0.5-0.1.hum12026-07-22redhat

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:6.0.15-1 ... 5:6.0.16-1~bpo11+1 (12 versions)
  • every version up to 5:6.0.16-1+deb11u9: fixed in 5:6.0.16-1+deb11u9
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:7.0.11-1 ... 5:7.0.15-1~deb12u8 (16 versions)
  • every version up to 5:7.0.15-1~deb12u9: fixed in 5:7.0.15-1~deb12u9
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:8.0.2-3 ... 5:8.6.3-1 (11 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
redis5:8.0.2-3 ... 5:8.6.3-1 (9 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 360 rows 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. None are among the latest 100 rows. The 260 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  3. 2026-11-11 20:58 UTCEchelonGraph re-scored
  4. 2026-11-11 20:58 UTCVendor advisory
  5. 2026-11-11 20:58 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  7. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  8. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  9. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  10. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  11. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  12. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.9% · 59th percentile
  14. 2026-11-04 13:57 UTCEchelonGraph re-scored
  15. 2026-11-04 13:57 UTCVendor advisory
  16. 2026-11-04 13:57 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  22. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  23. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  24. 2026-10-28 07:22 UTCEchelonGraph re-scored
  25. 2026-10-28 07:22 UTCVendor advisory
Show 75 more
  1. 2026-10-28 07:22 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  2. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  3. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  4. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  5. 2026-10-25 14:11 UTCEchelonGraph re-scored
  6. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  7. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  8. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  9. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  10. 2026-10-20 18:39 UTCEchelonGraph re-scored
  11. 2026-10-20 18:39 UTCVendor advisory
  12. 2026-10-20 18:39 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  14. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  15. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  16. 2026-10-18 03:21 UTCEchelonGraph re-scored
  17. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  18. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  19. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  20. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.9% · 58th percentile
  21. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  22. 2026-10-13 10:56 UTCEchelonGraph re-scored
  23. 2026-10-13 10:56 UTCVendor advisory
  24. 2026-10-13 10:56 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  26. 2026-10-12 15:46 UTCEchelonGraph re-scored
  27. 2026-10-11 19:31 UTCEchelonGraph re-scored
  28. 2026-10-11 16:46 UTCEchelonGraph re-scored
  29. 2026-10-11 14:07 UTCEchelonGraph re-scored
  30. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  31. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  32. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  33. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  34. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  35. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  36. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  37. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  38. 2026-10-04 07:41 UTCEchelonGraph re-scored
  39. 2026-10-04 07:41 UTCVendor advisory
  40. 2026-10-04 07:41 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  41. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  42. 2026-10-02 19:42 UTCEchelonGraph re-scored
  43. 2026-10-02 19:42 UTCVendor advisory
  44. 2026-10-02 19:42 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  45. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  46. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  47. 2026-10-01 04:31 UTCEchelonGraph re-scored
  48. 2026-10-01 04:31 UTCVendor advisory
  49. 2026-10-01 04:31 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  50. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  51. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  52. 2026-09-28 04:25 UTCEchelonGraph re-scored
  53. 2026-09-28 04:25 UTCVendor advisory
  54. 2026-09-28 04:25 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.9% · 57th percentile
  56. 2026-09-25 09:59 UTCEchelonGraph re-scored
  57. 2026-09-25 09:59 UTCVendor advisory
  58. 2026-09-25 09:59 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-09-24 11:00 UTCVendor advisory
  60. 2026-09-24 10:59 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  61. 2026-09-23 22:35 UTCEchelonGraph re-scored
  62. 2026-09-23 22:35 UTCVendor advisory
  63. 2026-09-23 22:35 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  65. 2026-09-23 10:24 UTCVendor advisory
  66. 2026-09-23 10:24 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-09-22 22:09 UTCEchelonGraph re-scored
  68. 2026-09-22 22:09 UTCVendor advisory
  69. 2026-09-22 22:08 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  70. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  71. 2026-09-20 01:39 UTCEchelonGraph re-scored
  72. 2026-09-20 01:39 UTCVendor advisory
  73. 2026-09-20 01:39 UTCGHSA enrichmentGHSA-c964-568j-vxx7 · GitHub severity HIGH · GitHub CVSS 7.5
  74. 2026-09-18 22:27 UTCEchelonGraph re-scored
  75. 2026-09-18 22:27 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-66373?
CVE-2026-66373 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-66373 published?
The CVE record for CVE-2026-66373 was published on July 25, 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-66373 actively exploited?
CVE-2026-66373 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (59th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-66373?
CVE-2026-66373 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-66373?
A fix for CVE-2026-66373 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-66373 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-66373

Explore →

Is Your Infrastructure Affected by CVE-2026-66373?

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