CVE-2025-62507VulnerabilityPublished 7 Nov 2025Updated 8 Sep 2026

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

Affects redisSource GCVE Database

Not known to be exploited : upgrade to 8.2.3 soon.

Data as of 25 Oct 2026, 19:02 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 7.4% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.2.3

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redis to 8.2.3.

Patches and advisories

github.com/redis/redis/commit/5f83972188f6e5b1d6f1940218c650a9cbdf7741 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Bitnamiredis`pkg:bitnami/redis`Other threats	Affected >=8.2.0 <8.2.3	Fixed in 8.2.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and the issue is fixed in Redis version 8.2.3. Users are advised to upgrade to this version to remediate the vulnerability. As a temporary workaround, administrators can restrict the execution of the XACKDEL command using ACLs to prevent exploitation until the patch can be applied.

Description

A vulnerability in Redis versions 8.2.0 through 8.2.2 allows a user to trigger a stack buffer overflow by running the XACKDEL command with multiple IDs. This flaw may lead to remote code execution. The issue is fixed in Redis version 8.2.3. As a workaround, administrators can restrict the XACKDEL command using ACLs to prevent exploitation without applying the patch.

References

Community reviews

Loading reviews…