CVE-2026-25243: redis-server RESTORE invalid memory access may allow remote code execution
Noroxi assessment
Priority: Monitor (action score 31/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: 4% (FIRST EPSS); higher than 90.5% 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 versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.
- BDU:2026-06448
- ALSA-2026:23229
- ALSA-2026:25216
- ALSA-2026:25219
- ALSA-2026:25925
- ALSA-2026:26008
- openSUSE-SU-2026:10711-1
- openSUSE-SU-2026:10719-1
- openSUSE-SU-2026:21612-1
- RHSA-2026:14316
- RHSA-2026:23229
- RHSA-2026:25216
- RHSA-2026:25219
- RHSA-2026:25925
- RHSA-2026:26008
- RHSA-2026:26233
- RHSA-2026:26306
- RHSA-2026:26540
- RHSA-2026:27716
- RHSA-2026:27787
- Published
- May 5, 2026
- Updated
- Jul 25, 2026
- EPSS
- 4.0% · 90th percentile
- CWE
- CWE-122
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.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
- 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.
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
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 helpAffected 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 scanAffected 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:8 | redis | before 6.2.22-1.module_el8.10.0+4197+3446deec | 6.2.22-1.module_el8.10.0+4197+3446deec |
| AlmaLinux:8 | redis-devel | before 6.2.22-1.module_el8.10.0+4197+3446deec | 6.2.22-1.module_el8.10.0+4197+3446deec |
| AlmaLinux:8 | redis-doc | before 6.2.22-1.module_el8.10.0+4197+3446deec | 6.2.22-1.module_el8.10.0+4197+3446deec |
| 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 | before 6.2.22-1.el9_8 | 6.2.22-1.el9_8 |
| AlmaLinux:9 | redis-devel | before 6.2.22-1.el9_8 | 6.2.22-1.el9_8 |
| 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 | redis-doc | before 6.2.22-1.el9_8 | 6.2.22-1.el9_8 |
| 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 |
+80
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
Published before and after this one in the same product
- ← EarlierCVE-2026-23479May 5, 2026 · redis-server use-after-free in unblock client flow may allow remote code execution30Monitor
- ← EarlierCVE-2026-23631May 5, 2026 · redis-server Lua use-after-free may allow remote code execution25Monitor
- Later →CVE-2026-66373Jul 24, 2026 · Redis before 8.8.0, in the unusual case where an authenticated attacker can execute RESTORE, allows remote code execution via a RESTORE payl30Monitor
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 | 6.2.22-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:redis-devel | 6.2.22-1.el9_8 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:redis-doc | 6.2.22-1.el9_8 · 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:6.2.22-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-debuginfo | 0:6.2.22-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-debugsource | 0:6.2.22-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-devel | 0:6.2.22-1.el9_8 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-doc | 0:6.2.22-1.el9_8 · 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:6.2.22-1.el9_8 · 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 ×3
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:13 | 2026-06-13 |
| Proof-of-concept repository on GitHub | stars:2 | 2026-07-02 |
| Proof-of-concept repository on GitHub | stars:1 | 2026-08-06 |
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+38 d
- TodayOct 28, 2026+176 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.
No nightly-computed relations.
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-122 · Heap-based Buffer OverflowCVSS 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
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- github.com/redis/redis/security/advisories/GHSA-c8h9-259x-jff4
- access.redhat.com/errata/RHSA-2026:14316
- access.redhat.com/errata/RHSA-2026:23229
- 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:26008
- access.redhat.com/errata/RHSA-2026:26233
- access.redhat.com/errata/RHSA-2026:26306
- access.redhat.com/errata/RHSA-2026:26540
- access.redhat.com/errata/RHSA-2026:27716
- access.redhat.com/errata/RHSA-2026:27787
- access.redhat.com/errata/RHSA-2026:28139
- access.redhat.com/errata/RHSA-2026:28142
- access.redhat.com/errata/RHSA-2026:29817
- access.redhat.com/errata/RHSA-2026:33427
- access.redhat.com/security/cve/CVE-2026-25243
- bugzilla.redhat.com/show_bug.cgi?id=2466828
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25243.json
Vendor advisories and official records. Exploit/PoC links are deliberately left out.