CVE-2026-23479

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 1.3%, top 32% 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.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: None knownExposed: 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)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
70%
KEV
Not listed

Published

May 5, 2026

Last Modified

July 25, 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

Vendor Advisories for CVE-2026-23479(8)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatvalkey-0:8.0.9-1.el10_02026-06-17redhat
redhatredis:7-9060020260602115714.92026-06-16redhat
redhatvalkey-0:8.0.9-1.el9_82026-06-15redhat
redhatredis:7-9080020260521083756.92026-06-11redhat
redhatvalkey-0:8.0.9-1.el10_22026-06-11redhat
redhatvalkey-main-9.0.4-0.1.hum12026-05-06redhat
redhatboost-main-1.90.0-7.hum12026-04-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.

Affected Packages

(7 across 7 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
valkey—7.2.13-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
valkey—7.2.13-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
valkey—8.1.7-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
valkey—9.0.4-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
valkey—9.0.4-r0—
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 6× in last 7d / 55× 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 203 total refreshes for this CVE.

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

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 July 25, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 30.2% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs