# CVE-2025-62507: Redis: Bug in XACKDEL may lead to stack overflow and potential RCE

> A stack buffer overflow in Redis XACKDEL command allows remote attackers to potentially execute arbitrary code.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 4 Nov 2025
- **Updated:** 26 Feb 2026
- **Also known as:** BELL-CVE-2025-62507, BIT-keydb-2025-62507, BIT-redis-2025-62507, GHSA-jhjx-x4cf-4vm8, MINI-mfjf-rjj4-v6w5, openSUSE-SU-2025:15698-1

## What is CVE-2025-62507?

CVE-2025-62507 is a high-severity memory corruption vulnerability in redis, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Redis is an open source, in-memory database that persists on disk. In versions 8.2.0 and above, a user can run the XACKDEL command with multiple ID's and trigger a stack buffer overflow, which may potentially lead to remote code execution. This issue is fixed in version 8.2.3. To workaround this issue without patching the redis-server executable is to prevent users from executing XACKDEL operation. This can be done using ACL to restrict XACKDEL command.

Weakness: CWE-787 (Out-of-bounds Write), CWE-20 (Improper Input Validation), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-62507?

2 open source packages ship an affected version, including redis and keydb. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `redis` | Bitnami | From 8.2.0 | 8.2.3 |
| `keydb` | Bitnami | From 8.2.0 | 8.2.3 |
| `redis` | openSUSE:Tumbleweed | All versions | 8.2.3-1.1 |

Products: Redis Redis.

## How do I fix CVE-2025-62507?

Upgrade redis to 8.2.3 or later.

## Is CVE-2025-62507 being exploited?

There is no known exploitation of CVE-2025-62507 in the wild and no public exploit code.

Public exploit code:

- https://github.com/GartonChan/redis-cve-2025-62507 (github_poc): https://github.com/GartonChan/redis-cve-2025-62507

## 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-2026-25243](https://insights.sbomify.com/CVE-2026-25243/): redis-server RESTORE invalid memory access may allow remote code execution (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-2025-62507 and fix it if it is affected.

What it is: CVE-2025-62507 is a high-severity memory corruption vulnerability in redis, published on 4 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62507 in the wild and no public exploit code.

Affected packages and fixed versions:
- redis (Bitnami): affected from 8.2.0; fixed in 8.2.3
- keydb (Bitnami): affected from 8.2.0; fixed in 8.2.3

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-2025-62507/ (Markdown: https://insights.sbomify.com/CVE-2025-62507/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62507
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62507
- OSV: https://osv.dev/vulnerability/CVE-2025-62507

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62507/
Summaries are generated and may contain mistakes; the official description above is the record.