# CVE-2026-23631: redis-server Lua use-after-free may allow remote code execution

> An authenticated attacker can trigger a use-after-free in Redis replicas with read-only disabled, potentially leading to remote code execution.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 May 2026
- **Updated:** 16 Jul 2026
- **Also known as:** ALPINE-CVE-2026-23631, AZL-86084, BELL-CVE-2026-23631, BIT-keydb-2026-23631, BIT-redis-2026-23631, BIT-valkey-2026-23631, CLSA-2026-1779351595, DEBIAN-CVE-2026-23631, GHSA-8ghh-qpmp-7826, MINI-8462-q4p6-qfgh, MINI-cph2-8q3f-9mx2, MINI-gqw7-jxpf-9wj4, MINI-pxp7-5g4q-833r, MINI-w92g-9hw8-cfgv, MINI-wwcf-rch4-jqqj, RHSA-2026:33444, UBUNTU-CVE-2026-23631

## What is CVE-2026-23631?

CVE-2026-23631 is a medium-severity use after free vulnerability in redis, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-23631?

3 open source packages ship an affected version, including redis, keydb and valkey. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | Bitnami | From 7.2.0 | 7.2.14, 7.4.9, 8.2.6, 8.4.3, 8.6.3 |
| `keydb` | Bitnami | From 7.2.0 | 7.2.14, 7.4.9, 8.2.6, 8.4.3, 8.6.3 |
| `valkey` | Bitnami | All versions | 7.2.13, 8.0.8, 8.1.7, 9.0.4 |
| `redis` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:7.0.12-2.module+el9.4.0+24450+e284b512.8 |
| `redis-debuginfo` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:7.0.12-2.module+el9.4.0+24450+e284b512.8 |
| `redis-debugsource` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:7.0.12-2.module+el9.4.0+24450+e284b512.8 |
| `redis-devel` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:7.0.12-2.module+el9.4.0+24450+e284b512.8 |
| `redis-doc` | Red Hat:rhel_e4s:9.4::appstream | All versions | 0:7.0.12-2.module+el9.4.0+24450+e284b512.8 |

Products: Redis Redis.

## How do I fix CVE-2026-23631?

Upgrade redis to a fixed version for your release line: 7.2.14, 7.4.9, 8.2.6 or 8.4.3.

## Is CVE-2026-23631 being exploited?

There is no known exploitation of CVE-2026-23631 in the wild and no public exploit code.

Public exploit code:

- CVE-2026-23631 (DarkReplica) Redis Exploit (github_poc): https://github.com/yoyosh/DarkReplica
- CVE-2026-23631-Draft (github_poc): https://github.com/HORKimhab/CVE-2026-23631

## Other vulnerabilities in redis

- [CVE-2022-0543](https://insights.sbomify.com/CVE-2022-0543/): Debian-specific Redis Server Lua Sandbox Escape (critical 10.0, exploited in the wild)
- [CVE-2026-23479](https://insights.sbomify.com/CVE-2026-23479/): redis-server use-after-free in unblock client flow may allow remote code execution (high 7.7)
- [CVE-2026-25243](https://insights.sbomify.com/CVE-2026-25243/): redis-server RESTORE invalid memory access may allow remote code execution (high 7.7)
- [CVE-2025-62507](https://insights.sbomify.com/CVE-2025-62507/): Redis: Bug in XACKDEL may lead to stack overflow and potential RCE (high 7.7)
- [CVE-2025-48367](https://insights.sbomify.com/CVE-2025-48367/): Redis DoS Vulnerability due to bad connection error handling (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23631 and fix it if it is affected.

What it is: CVE-2026-23631 is a medium-severity use after free vulnerability in redis, published on 5 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23631 in the wild and no public exploit code.

Affected packages and fixed versions:
- redis (Bitnami): affected from 7.2.0; fixed in 7.2.14, 7.4.9, 8.2.6, 8.4.3, 8.6.3
- keydb (Bitnami): affected from 7.2.0; fixed in 7.2.14, 7.4.9, 8.2.6, 8.4.3, 8.6.3
- valkey (Bitnami): affected all versions; fixed in 7.2.13, 8.0.8, 8.1.7, 9.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-23631/ (Markdown: https://insights.sbomify.com/CVE-2026-23631/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-23631
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-23631
- OSV: https://osv.dev/vulnerability/CVE-2026-23631

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-23631/
Summaries are generated and may contain mistakes; the official description above is the record.