CVE-2026-66373

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM 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
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

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.5(medium)
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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

July 25, 2026

Last Modified

September 9, 2026

Advisory Details (5)

Auto-updated Jul 25, 2026
Patch 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/2080059356322918777
generic

Kimi K3 exploited the latest Redis server | Hacker News

https://news.ycombinator.com/item?id=49024938
github_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/15081
generic

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

https://github.com/redis/redis/compare/8.6.4...8.8.0
generic

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

Vendor Advisories for CVE-2026-66373(8)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvalkey-0:8.0.11-1.el10_22026-09-08redhat
redhatredis:6-8100020260821173603.489197e62026-09-08redhat
redhatvalkey-0:8.0.10-1.el9_82026-09-08redhat
redhatredis-0:6.2.24-1.el9_82026-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 rangeFixed inDependents
redis5:6.0.15-1 ... 5:6.0.16-1~bpo11+1 (12 versions)5:6.0.16-1+deb11u9—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
redis5:7.0.11-1 ... 5:7.0.15-1~deb12u8 (16 versions)5:7.0.15-1~deb12u9—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
redis5:8.0.2-3 ... 5:8.6.3-1 (11 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
redis5:8.0.2-3 ... 5:8.6.3-1 (9 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 247 total refreshes for this CVE.

  1. 2026-09-15 09:33 UTCEG score recompute
  2. 2026-09-15 09:33 UTCVendor advisory
  3. 2026-09-15 09:33 UTCGHSA enrichment
  4. 2026-09-14 05:45 UTCVendor advisory
  5. 2026-09-14 05:45 UTCGHSA enrichment
  6. 2026-09-13 17:35 UTCEG score recompute
  7. 2026-09-13 17:35 UTCVendor advisory
  8. 2026-09-13 17:35 UTCGHSA enrichment
  9. 2026-09-13 05:24 UTCVendor advisory
  10. 2026-09-13 05:24 UTCGHSA enrichment
  11. 2026-09-12 17:13 UTCEG score recompute
  12. 2026-09-12 17:13 UTCVendor advisory
  13. 2026-09-12 17:13 UTCGHSA enrichment
  14. 2026-09-12 05:02 UTCVendor advisory
  15. 2026-09-12 05:02 UTCGHSA enrichment
  16. 2026-09-11 16:34 UTCEG score recompute
  17. 2026-09-11 16:34 UTCVendor advisory
  18. 2026-09-11 16:34 UTCGHSA enrichment
  19. 2026-09-11 14:53 UTCEPSS rescore
  20. 2026-09-11 09:37 UTCEPSS rescore
  21. 2026-09-11 02:29 UTCVendor advisory
  22. 2026-09-11 02:29 UTCGHSA enrichment
  23. 2026-09-10 13:33 UTCEG score recompute
  24. 2026-09-10 13:33 UTCVendor advisory
  25. 2026-09-10 13:33 UTCGHSA enrichment
Show 75 more
  1. 2026-09-09 16:19 UTCVendor advisory
  2. 2026-09-09 16:19 UTCGHSA enrichment
  3. 2026-09-09 08:42 UTCEG score recompute
  4. 2026-09-09 08:42 UTCVendor advisory
  5. 2026-09-09 08:42 UTCGHSA enrichment
  6. 2026-09-08 22:01 UTCEPSS rescore
  7. 2026-09-07 21:23 UTCEG score recompute
  8. 2026-09-07 21:23 UTCVendor advisory
  9. 2026-09-07 21:23 UTCGHSA enrichment
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 08:07 UTCVendor advisory
  13. 2026-09-06 08:07 UTCGHSA enrichment
  14. 2026-09-05 19:22 UTCEG score recompute
  15. 2026-09-05 19:22 UTCVendor advisory
  16. 2026-09-05 19:22 UTCGHSA enrichment
  17. 2026-09-05 15:31 UTCEPSS rescore
  18. 2026-09-05 06:52 UTCEG score recompute
  19. 2026-09-05 06:52 UTCVendor advisory
  20. 2026-09-05 06:52 UTCGHSA enrichment
  21. 2026-09-04 12:43 UTCEG score recompute
  22. 2026-09-04 12:43 UTCVendor advisory
  23. 2026-09-04 12:43 UTCGHSA enrichment
  24. 2026-09-04 05:07 UTCEPSS rescore
  25. 2026-09-02 14:12 UTCEPSS rescore
  26. 2026-09-01 23:15 UTCEG score recompute
  27. 2026-09-01 23:15 UTCVendor advisory
  28. 2026-09-01 23:15 UTCGHSA enrichment
  29. 2026-09-01 13:54 UTCEPSS rescore
  30. 2026-09-01 04:40 UTCEPSS rescore
  31. 2026-08-31 00:41 UTCEG score recompute
  32. 2026-08-31 00:41 UTCVendor advisory
  33. 2026-08-31 00:41 UTCGHSA enrichment
  34. 2026-08-30 19:17 UTCEPSS rescore
  35. 2026-08-30 12:30 UTCEG score recompute
  36. 2026-08-30 12:30 UTCVendor advisory
  37. 2026-08-30 12:30 UTCGHSA enrichment
  38. 2026-08-30 01:22 UTCEPSS rescore
  39. 2026-08-30 00:14 UTCEG score recompute
  40. 2026-08-30 00:14 UTCVendor advisory
  41. 2026-08-30 00:14 UTCGHSA enrichment
  42. 2026-08-28 21:42 UTCEPSS rescore
  43. 2026-08-27 23:21 UTCEG score recompute
  44. 2026-08-27 23:21 UTCVendor advisory
  45. 2026-08-27 23:21 UTCGHSA enrichment
  46. 2026-08-27 11:10 UTCVendor advisory
  47. 2026-08-27 11:10 UTCGHSA enrichment
  48. 2026-08-26 22:55 UTCEG score recompute
  49. 2026-08-26 22:55 UTCVendor advisory
  50. 2026-08-26 22:55 UTCGHSA enrichment
  51. 2026-08-26 14:47 UTCEPSS rescore
  52. 2026-08-26 10:44 UTCVendor advisory
  53. 2026-08-26 10:44 UTCGHSA enrichment
  54. 2026-08-25 22:33 UTCEG score recompute
  55. 2026-08-25 22:33 UTCVendor advisory
  56. 2026-08-25 22:33 UTCGHSA enrichment
  57. 2026-08-25 13:49 UTCEPSS rescore
  58. 2026-08-25 10:21 UTCVendor advisory
  59. 2026-08-25 10:21 UTCGHSA enrichment
  60. 2026-08-24 22:10 UTCEG score recompute
  61. 2026-08-24 22:10 UTCVendor advisory
  62. 2026-08-24 22:10 UTCGHSA enrichment
  63. 2026-08-24 09:59 UTCEG score recompute
  64. 2026-08-24 09:59 UTCVendor advisory
  65. 2026-08-24 09:59 UTCGHSA enrichment
  66. 2026-08-23 21:48 UTCVendor advisory
  67. 2026-08-23 21:48 UTCGHSA enrichment
  68. 2026-08-23 09:37 UTCEG score recompute
  69. 2026-08-23 09:37 UTCVendor advisory
  70. 2026-08-23 09:37 UTCGHSA enrichment
  71. 2026-08-23 00:19 UTCEPSS rescore
  72. 2026-08-22 21:27 UTCVendor advisory
  73. 2026-08-22 21:27 UTCGHSA enrichment
  74. 2026-08-22 09:16 UTCEG score recompute
  75. 2026-08-22 09:16 UTCVendor advisory

Related CVEs(same vendor + same CWE)

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 September 9, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 55.2% 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

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.

Start Free Scan →Browse All CVEs