CVE-2026-23479

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

Redis is an in-memory data structure store. In redis-server from 7.2.0 until 8.6.3, the unblock client flow does not handle an error return from processCommandAndResetClient when re-executing a blocked command. If a blocked client is evicted during this flow, an authenticated attacker can trigger a use-after-free that may lead to remote code execution. This has been patched in version 8.6.3.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
66.7%
KEV
Not listed

Published

May 5, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated May 5, 2026
Patch available. Sources: github.
github Patch Available

Use-After-Free in unblock client flow may lead to remote code execution · Advisory · redis/redis · GitHub

https://github.com/redis/redis/security/advisories/GHSA-93m2-935m-8rj3
generic

Release 8.6.3 · redis/redis · GitHub

https://github.com/redis/redis/releases/tag/8.6.3

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatredis:7-9080020260521083756.92026-06-11redhat
redhatvalkey-0:8.0.9-1.el10_22026-06-11redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 66× 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 118 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23479?
CVE-2026-23479 is a high vulnerability published on May 5, 2026. Redis is an in-memory data structure store. In redis-server from 7.2.0 until 8.6.3, the unblock client flow does not handle an error return from processCommandAndResetClient when re-executing a blocked command. If a blocked client is evicted during this flow, an authenticated attacker can trigger a…
When was CVE-2026-23479 disclosed?
CVE-2026-23479 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23479 actively exploited?
CVE-2026-23479 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 66.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23479?
CVE-2026-23479 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-23479?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23479, 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-23479

Explore →

Is Your Infrastructure Affected by CVE-2026-23479?

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