# 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. - **Severity:** High 7.7 (`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`) - **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-25243, ALSA-2026:23229, ALSA-2026:26008, AZL-86081, BELL-CVE-2026-25243, BIT-keydb-2026-25243, BIT-redis-2026-25243, BIT-valkey-2026-25243, DEBIAN-CVE-2026-25243, GHSA-c8h9-259x-jff4, MINI-2crm-639w-rrh8, MINI-f3r7-mv4c-235x, MINI-gmqg-w6rf-95q4, MINI-vqvh-jcpj-j4p3, MINI-x56g-6gpc-c2wc, MINI-xg4g-9j75-x3vp, MINI-xrrq-3mq6-q7q3, RHSA-2026:23229, RHSA-2026:26008, RHSA-2026:26233, RHSA-2026:27716, RHSA-2026:27787, RHSA-2026:28139, RHSA-2026:28142, RHSA-2026:29817, RHSA-2026:33427, RLSA-2026:23229, RLSA-2026:26008, SUSE-SU-2026:2098-1, UBUNTU-CVE-2026-25243 ## 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 (Heap-based Buffer Overflow) ## 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 | Ecosystem | 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 | | `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: 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. ## 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: - CVE-2026-25243 — Redis RESTORE zipmap double-free → remote code execution (ASLR on). (github_poc): https://github.com/dinosn/CVE-2026-25243 - https://github.com/dinosn/CVE-2026-25243-debugfree (github_poc): https://github.com/dinosn/CVE-2026-25243-debugfree - Stable POC for CVE-2026-25243 (Redis RESTORE double-free -> remote code execution) (github_poc): https://github.com/captain-woof/CVE-2026-25243 ## 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-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) - [CVE-2023-31655](https://insights.sbomify.com/CVE-2023-31655/): Denial of service in n/a (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-25243 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-25243 in the wild and no public exploit code. Affected packages and fixed versions: - redis (Bitnami): affected all versions; fixed in 6.2.22, 7.2.14, 7.4.9, 8.2.6, 8.4.3, 8.6.3 - keydb (Bitnami): affected all versions; fixed in 6.2.22, 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-25243/ (Markdown: https://insights.sbomify.com/CVE-2026-25243/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-25243 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-25243 - OSV: https://osv.dev/vulnerability/CVE-2026-25243 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-25243/ Summaries are generated and may contain mistakes; the official description above is the record.