CVE-2026-25243 redis-server RESTORE invalid memory access may allow remote code execution
An authenticated attacker can trigger remote code execution in Redis by sending a crafted payload to the RESTORE command due to improper validation.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-25243?
CVE-2026-25243 is a high-severity memory corruption 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 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.
Weakness: CWE-122
Which versions are affected by CVE-2026-25243?
3 open source packages ship an affected version, including redis, keydb and valkey. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
redis Bitnami | All versions | 6.2.22, 7.2.14, 7.4.9, 8.2.6, 8.4.3, 8.6.3 |
keydb Bitnami | All versions | 6.2.22, 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 |
Linux distribution packages (37)
redis AlmaLinux:8 | All versions | 6.2.22-1.module_el8.10.0+4197+3446deec |
redis-devel AlmaLinux:8 | All versions | 6.2.22-1.module_el8.10.0+4197+3446deec |
redis-doc AlmaLinux:8 | All versions | 6.2.22-1.module_el8.10.0+4197+3446deec |
redis AlmaLinux:9 | All versions | 6.2.22-1.el9_8 |
redis-devel AlmaLinux:9 | All versions | 6.2.22-1.el9_8 |
redis-doc AlmaLinux:9 | All versions | 6.2.22-1.el9_8 |
redis Red Hat:enterprise_linux:8::appstream | All versions | 0:6.2.22-1.module+el8.10.0+24332+dbd3b426 |
redis-debuginfo Red Hat:enterprise_linux:8::appstream | All versions | 0:6.2.22-1.module+el8.10.0+24332+dbd3b426 |
redis-debugsource Red Hat:enterprise_linux:8::appstream | All versions | 0:6.2.22-1.module+el8.10.0+24332+dbd3b426 |
redis-devel Red Hat:enterprise_linux:8::appstream | All versions | 0:6.2.22-1.module+el8.10.0+24332+dbd3b426 |
redis-doc Red Hat:enterprise_linux:8::appstream | All versions | 0:6.2.22-1.module+el8.10.0+24332+dbd3b426 |
redis Red Hat:enterprise_linux:9::appstream | All versions | 0:6.2.22-1.el9_8 |
redis-debuginfo Red Hat:enterprise_linux:9::appstream | All versions | 0:6.2.22-1.el9_8 |
redis-debugsource Red Hat:enterprise_linux:9::appstream | All versions | 0:6.2.22-1.el9_8 |
redis-devel Red Hat:enterprise_linux:9::appstream | All versions | 0:6.2.22-1.el9_8 |
redis-doc Red Hat:enterprise_linux:9::appstream | All versions | 0:6.2.22-1.el9_8 |
redis Red Hat:rhel_aus:8.4::appstream | All versions | 0:6.0.9-5.module+el8.4.0+24416+a7ffbc5f.6 |
redis-debuginfo Red Hat:rhel_aus:8.4::appstream | All versions | 0:6.0.9-5.module+el8.4.0+24416+a7ffbc5f.6 |
redis-debugsource Red Hat:rhel_aus:8.4::appstream | All versions | 0:6.0.9-5.module+el8.4.0+24416+a7ffbc5f.6 |
redis-devel Red Hat:rhel_aus:8.4::appstream | All versions | 0:6.0.9-5.module+el8.4.0+24416+a7ffbc5f.6 |
redis-doc Red Hat:rhel_aus:8.4::appstream | All versions | 0:6.0.9-5.module+el8.4.0+24416+a7ffbc5f.6 |
redis Red Hat:rhel_aus:8.6::appstream | All versions | 0:6.0.9-5.module+el8.6.0+24434+c7b1e4bc.7 |
redis-debuginfo Red Hat:rhel_aus:8.6::appstream | All versions | 0:6.0.9-5.module+el8.6.0+24434+c7b1e4bc.7 |
redis-debugsource Red Hat:rhel_aus:8.6::appstream | All versions | 0:6.0.9-5.module+el8.6.0+24434+c7b1e4bc.7 |
redis-devel Red Hat:rhel_aus:8.6::appstream | All versions | 0:6.0.9-5.module+el8.6.0+24434+c7b1e4bc.7 |
redis-doc Red Hat:rhel_aus:8.6::appstream | All versions | 0:6.0.9-5.module+el8.6.0+24434+c7b1e4bc.7 |
redis Red Hat:rhel_e4s:8.8::appstream | All versions | 0:6.2.7-1.module+el8.8.0+24465+9d14ca70.7 |
redis-debuginfo Red Hat:rhel_e4s:8.8::appstream | All versions | 0:6.2.7-1.module+el8.8.0+24465+9d14ca70.7 |
redis-debugsource Red Hat:rhel_e4s:8.8::appstream | All versions | 0:6.2.7-1.module+el8.8.0+24465+9d14ca70.7 |
redis-devel Red Hat:rhel_e4s:8.8::appstream | All versions | 0:6.2.7-1.module+el8.8.0+24465+9d14ca70.7 |
redis-doc Red Hat:rhel_e4s:8.8::appstream | All versions | 0:6.2.7-1.module+el8.8.0+24465+9d14ca70.7 |
redis Red Hat:rhel_e4s:9.2::appstream | All versions | 0:6.2.7-1.el9_2.6 |
redis-debuginfo Red Hat:rhel_e4s:9.2::appstream | All versions | 0:6.2.7-1.el9_2.6 |
redis-debugsource Red Hat:rhel_e4s:9.2::appstream | All versions | 0:6.2.7-1.el9_2.6 |
redis-devel Red Hat:rhel_e4s:9.2::appstream | All versions | 0:6.2.7-1.el9_2.6 |
redis-doc Red Hat:rhel_e4s:9.2::appstream | All versions | 0:6.2.7-1.el9_2.6 |
redis Red Hat:rhel_e4s:9.4::appstream | All versions | 0:6.2.7-1.el9_4.6 |
Products include Redis Redis.
How do I fix CVE-2026-25243?
Upgrade redis to a fixed version for your release line: 6.2.22, 7.2.14, 7.4.9 or 8.2.6.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-25243 being exploited?
There is no known exploitation of CVE-2026-25243 in the wild and no public exploit code.
Public exploit code: 3 proofs of concept on GitHub.
Other vulnerabilities in redis
- CVE-2022-0543 Debian-specific Redis Server Lua Sandbox Escape
- CVE-2026-23479 redis-server use-after-free in unblock client flow may allow remote code execution
- CVE-2025-62507 Redis: Bug in XACKDEL may lead to stack overflow and potential RCE
- CVE-2025-48367 Redis DoS Vulnerability due to bad connection error handling
- CVE-2023-31655 Denial of service in n/a
Sources
Also known as ALPINE-CVE-2026-25243, ALSA-2026:23229, ALSA-2026:26008, AZL-86081, BELL-CVE-2026-25243, BIT-keydb-2026-25243 and 24 more.