redis-server use-after-free in unblock client flow may allow remote code execution
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.
- Published
- May 5, 2026
- Updated
- Jul 25, 2026
- EPSS
- 1.5% · 73th percentile
- CWE
- CWE-416
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.5%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 7.7
- 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:H/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.
Affected systems
| 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)
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redis redis7.2.0 and later · before 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
- >= 7.2.0, < 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:13 | redis | all versions | — |
| Debian:14 | redis | before 5:8.0.6-3 | 5:8.0.6-3 |
| 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 |
| Red Hat:enterprise_linux:10.2 | valkey | before 0:8.0.9-1.el10_2 | 0:8.0.9-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | valkey-debuginfo | before 0:8.0.9-1.el10_2 | 0:8.0.9-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | valkey-debugsource | before 0:8.0.9-1.el10_2 | 0:8.0.9-1.el10_2 |
| Red Hat:enterprise_linux:10.2 | valkey-devel | before 0:8.0.9-1.el10_2 | 0:8.0.9-1.el10_2 |
+21
Same product
redis: all recordsOther 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 escapeKEV100Now
- CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution64This week
- CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis58Plan
- CVE-2022-24834Heap overflow issue with the Lua cjson library used by Redis47Plan
- CVE-2023-22458Integer overflow in multiple Redis commands can lead to denial-of-service44Plan
- CVE-2024-46981Redis' Lua library commands may lead to remote code execution41Plan
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:8.0.6-3 · 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:boost | 0:1.90.0-7.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| Red Hat:boost-build | 0:1.90.0-7.hum1 · Red Hat:hummingbird:1 | 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-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) |
| 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 ×4
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.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-06-04 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-06-11 |
| Proof-of-concept repository on GitHub | stars:0 | 2026-08-04 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-08-19 |
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.
- Published
- First PoC+29 d
- TodaySep 29, 2026+147 d
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 researchersFinders, 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 execution64This week
- CVE-2024-46981484 days apartRedis' Lua library commands may lead to remote code execution41Plan
- CVE-2026-81934114 days apartRedis TLS pending-data list use-after-free30Monitor
- CVE-2026-236310 days apartredis-server Lua use-after-free may allow remote code execution25Monitor
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
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 FreeCVSS vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/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 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/redis/redis/releases/tag/8.6.3
- github.com/redis/redis/security/advisories/GHSA-93m2-935m-8rj3
- access.redhat.com/errata/RHSA-2026:14316
- access.redhat.com/errata/RHSA-2026:25216
- access.redhat.com/errata/RHSA-2026:25219
- access.redhat.com/errata/RHSA-2026:25925
- access.redhat.com/errata/RHSA-2026:26306
- access.redhat.com/errata/RHSA-2026:26540
- access.redhat.com/errata/RHSA-2026:7662
- access.redhat.com/security/cve/CVE-2026-23479
- bugzilla.redhat.com/show_bug.cgi?id=2466780
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-23479.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.