Skip to content
Fencer Vulns
high 8.8

CVE-2025-62507 json

Redis: Bug in XACKDEL may lead to stack overflow and potential RCE

published 2025-11-02 12 mo ago modified 2026-10-19 20 d ago also BIT-keydb-2025-62507 , BIT-redis-2025-62507 , EUVD-2025-37903 , GHSA-jhjx-x4cf-4vm8

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
7.5%
EPSS 7.5% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami keydb 8.2.3
  • bitnami redis 8.2.3
  • redis redis 8.2.3
  • redislabs redis 8.2.3
  • redis openSUSE Leap 16.0 8.2.3-bp160.1.1
  • redis openSUSE Tumbleweed 8.2.3-1.1

opensuse advisories openSUSE-SU-2025:20121-1openSUSE-SU-2025:15698-1

  • redis Alpine 3.24, Alpine 3.23 8.2.3-r0

alpine advisories ALPINE-CVE-2025-62507

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-62507 updated cvss 8.8

redis: Redis: Bug in XACKDEL may lead to stack overflow and potential RCE

  • Red Hat Enterprise Linux 8 redis Red Hat Enterprise Linux 9 redis
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
12 mo ago

Exploit prediction

7.47% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 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
CNA 4.0 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/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 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami keydb
>=8.2.0, <8.2.3
8.2.3
bitnami redis
>=8.2.0, <8.2.3
8.2.3

Affected products

  • redis redis

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of redis/redis published their own advisory on GitHub. Reviewed sources take precedence over it.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.