CVE-2026-23631

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 2.8%, top 15% 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
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Redis is an in-memory data structure store. In all versions of redis-server with Lua scripting, an authenticated attacker can exploit the master-replica synchronization mechanism to trigger a use-after-free on replicas where replica-read-only is disabled or can be disabled, which may lead to remote code execution. A workaround is to prevent users from executing Lua scripts or avoid using replicas where replica-read-only is disabled. This is patched in version 8.6.3.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
86%
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

Lua Use-After-Free may lead to remote code execution · Advisory · redis/redis · GitHub

https://github.com/redis/redis/security/advisories/GHSA-8ghh-qpmp-7826
generic

Release 8.6.3 · redis/redis · GitHub

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatredis:7-9040020260625094332.92026-06-30redhat
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

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

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
valkey7.2.13-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
valkey7.2.13-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
valkey8.1.7-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
valkey9.0.4-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
valkey9.0.4-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
redis5:6.0.15-1 ... 5:8.6.3-1 (103 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
redis5:7.0.11-1 ... 5:7.0.15-1~deb12u7 (15 versions)5:7.0.15-1~deb12u8
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 4× in last 7d / 26× 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 221 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCyoyosh/DarkReplica
    First seen May 7, 2026

    CVE-2026-23631 (DarkReplica) Redis Exploit

    Open source ↗

Frequently asked(5)

What is CVE-2026-23631?
CVE-2026-23631 is a high vulnerability published on May 5, 2026. Redis is an in-memory data structure store. In all versions of redis-server with Lua scripting, an authenticated attacker can exploit the master-replica synchronization mechanism to trigger a use-after-free on replicas where replica-read-only is disabled or can be disabled, which may lead to remote…
When was CVE-2026-23631 disclosed?
CVE-2026-23631 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-23631 actively exploited?
CVE-2026-23631 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 14.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23631?
CVE-2026-23631 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-23631?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23631, 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-23631

Explore →

Is Your Infrastructure Affected by CVE-2026-23631?

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