NVD / CVE Program· CNA GitHub_M

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

Noroxi assessment

Priority: Monitor (action score 25/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 3% (FIRST EPSS); higher than 87.7% of all records.
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
Fixed version: redis redis 8.6.3.

Low priority for now. Upgrade to redis redis 8.6.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.1 · v4.0—Proof of concept Fix available

Published: May 5, 2026
Updated: Jul 25, 2026
EPSS: 3.0% · 87th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 24 / 40 · 6.1 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 3.0%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.1; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
redis	redis	cpe:2.3:a:redis:redis

Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)

Is Redis on your server exposed to the internet?

The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.

Run a port scan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

redis redisbefore 8.6.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

redis redis
- < 8.6.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	valkey	before 8.0.9-1.el10_2	8.0.9-1.el10_2
AlmaLinux:10	valkey-devel	before 8.0.9-1.el10_2	8.0.9-1.el10_2
AlmaLinux:9	redis	before 7.2.14-1.module_el9.8.0+258+b8f945d3	7.2.14-1.module_el9.8.0+258+b8f945d3
AlmaLinux:9	redis-devel	before 7.2.14-1.module_el9.8.0+258+b8f945d3	7.2.14-1.module_el9.8.0+258+b8f945d3
AlmaLinux:9	redis-doc	before 7.2.14-1.module_el9.8.0+258+b8f945d3	7.2.14-1.module_el9.8.0+258+b8f945d3
AlmaLinux:9	valkey	before 8.0.9-1.el9_8	8.0.9-1.el9_8
AlmaLinux:9	valkey-devel	before 8.0.9-1.el9_8	8.0.9-1.el9_8
Alpine:v3.20	valkey	before 7.2.13-r0	7.2.13-r0
Alpine:v3.22	valkey	before 8.1.7-r0	8.1.7-r0
Alpine:v3.23	valkey	before 9.0.4-r0	9.0.4-r0
Debian:12	redis	before 5:7.0.15-1~deb12u8	5:7.0.15-1~deb12u8
Debian:13	redis	before 5:8.0.2-3+deb13u3	5:8.0.2-3+deb13u3
Debian:13	valkey	before 8.1.1+dfsg1-3+deb13u3	8.1.1+dfsg1-3+deb13u3
Debian:14	redict	from 0	—
Debian:14	redis	before 5:8.0.6-3	5:8.0.6-3
Debian:14	valkey	before 9.1.1-1	9.1.1-1
openSUSE:Leap 16.0	redis	before 8.10.1-bp160.1.1	8.10.1-bp160.1.1
openSUSE:Leap 16.0	redis-modules	before 8.10.1-bp160.1.1	8.10.1-bp160.1.1
openSUSE:Tumbleweed	redis	before 8.6.3-1.1	8.6.3-1.1
openSUSE:Tumbleweed	valkey	before 9.0.4-1.1	9.0.4-1.1
Red Hat:enterprise_linux_eus:10.0	valkey	before 0:8.0.9-1.el10_0	0:8.0.9-1.el10_0
Red Hat:enterprise_linux_eus:10.0	valkey-debuginfo	before 0:8.0.9-1.el10_0	0:8.0.9-1.el10_0
Red Hat:enterprise_linux_eus:10.0	valkey-debugsource	before 0:8.0.9-1.el10_0	0:8.0.9-1.el10_0
Red Hat:enterprise_linux_eus:10.0	valkey-devel	before 0:8.0.9-1.el10_0	0:8.0.9-1.el10_0

+32

Same product

redis: all records

Other highest-scoring records for the same primary product.

CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escapeKEV
100Now
CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution
64This week
CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis
58Plan

Published before and after this one in the same product

← EarlierCVE-2025-62507Nov 4, 2025 · Redis: Bug in XACKDEL may lead to stack overflow and potential RCE
32Monitor
← EarlierCVE-2026-23479May 5, 2026 · redis-server use-after-free in unblock client flow may allow remote code execution
31Monitor
Later →CVE-2026-25243May 5, 2026 · redis-server RESTORE invalid memory access may allow remote code execution
31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
redis redis	8.6.3 · description	Vendor (CNA)
almalinux:redis	7.2.14-1.module_el9.8.0+258+b8f945d3 · AlmaLinux:9	Package registry (OSV)
almalinux:redis-devel	7.2.14-1.module_el9.8.0+258+b8f945d3 · AlmaLinux:9	Package registry (OSV)
almalinux:redis-doc	7.2.14-1.module_el9.8.0+258+b8f945d3 · AlmaLinux:9	Package registry (OSV)
almalinux:valkey	8.0.9-1.el10_2 · AlmaLinux:10	Package registry (OSV)
almalinux:valkey-devel	8.0.9-1.el10_2 · AlmaLinux:10	Package registry (OSV)
alpine:valkey	7.2.13-r0 · Alpine:v3.20	Package registry (OSV)
debian:redis	5:7.0.15-1~deb12u8 · Debian:12	Package registry (OSV)
debian:valkey	8.1.1+dfsg1-3+deb13u3 · Debian:13	Package registry (OSV)
debian:valkey	9.1.1-1 · Debian:14	Package registry (OSV)
opensuse:redis	8.6.3-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
opensuse:redis-modules	8.10.1-bp160.1.1 · openSUSE:Leap 16.0	Package registry (OSV)
opensuse:valkey	9.0.4-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:redis	0:7.2.14-1.module+el9.8.0+24327+41ceb644 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:redis-debuginfo	0:7.2.14-1.module+el9.8.0+24327+41ceb644 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:redis-debugsource	0:7.2.14-1.module+el9.8.0+24327+41ceb644 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:redis-devel	0:7.2.14-1.module+el9.8.0+24327+41ceb644 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:redis-doc	0:7.2.14-1.module+el9.8.0+24327+41ceb644 · Red Hat:enterprise_linux:9::appstream	Package registry (OSV)
red hat:valkey	0:9.0.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:valkey-compat-redis	0:9.0.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:valkey-compat-redis-devel	0:9.0.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:valkey-debuginfo	0:8.0.9-1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:valkey-debugsource	0:8.0.9-1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:valkey-devel	0:8.0.9-1.el10_2 · Red Hat:enterprise_linux:10.2	Package registry (OSV)
red hat:valkey-devel	0:9.0.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:valkey-doc	0:9.0.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:valkey-rdma	0:9.0.4-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
rocky linux:redis	0:7.2.14-1.module+el9.8.0+40207+e2014501 · Rocky Linux:9	Package registry (OSV)
rocky linux:valkey	0:8.0.9-1.el10_2 · Rocky Linux:10	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:33	2026-05-07
Proof-of-concept repository on GitHub	stars:0	2026-06-04

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMay 5, 2026
First PoCMay 7, 2026+1 d
TodayNov 7, 2026+186 d

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-49844214 days apartRedis Lua Use-After-Free may lead to remote code execution
64This week
CVE-2024-46981484 days apartRedis' Lua library commands may lead to remote code execution
41Plan
CVE-2026-234790 days apartredis-server use-after-free in unblock client flow may allow remote code execution
31Monitor
CVE-2026-81934114 days apartRedis TLS pending-data list use-after-free
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

Redis VDPHackerOne · disclosure only (VDP)

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
Special conditions such as timing or configuration are required.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:47 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Show all references (11 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records

Noroxi analysis

What does it mean in your environment?

We use this product, ask for help

Data sources and verification

CNA: GitHub_M

CVE.org (CNA)Jul 16, 2026, 12:04 PM UTC
CISA ADPJul 16, 2026, 12:04 PM UTC
NVDJul 25, 2026, 7:10 AM UTC
FIRST EPSSNov 6, 2026, 12:00 AM UTC
OSV / GHSANov 7, 2026, 3:18 AM UTC
PoC-in-GitHubNov 7, 2026, 3:18 AM UTC

Each line is when that source was last processed for this record.

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

Noroxi assessment

Get told when this record changes

Follow CVE-2026-23631

What does it mean in your environment?

Affected systems

Is your version affected?

Watch new CVEs for redis

Affected versions

Versions reported by the vendor

Package-level exposure

Same product

Remediation

Which version to upgrade to

Exploit status

Research context

Timeline

Patch and commit links

Credits

Variant candidates

Chain candidates

Technical details

Attack conditions

If successful

Root cause

The bug in code

Attack context

Change log

References