CVE-2026-25588: redis · RedisTimeSeries RESTORE invalid memory access may allow remote code execution
Affects redisSource GCVE Database
Not known to be exploited · fixed in 8.6.3 : patch redis soon.
Data as of 26 Oct 2026, 10:12 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 8.6.3, 8.4.3, 8.2.6
Exploitation evidence
Disclosed: evidence found.
CVE published 7 May 2026
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 26 Oct 2026.
What to do
Upgrade redis to 8.6.3, 8.4.3 or 8.2.6.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamiredispkg:bitnami/redisOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Apply the official patch by upgrading RedisTimeSeries to version 1.12.14 or later. Until patched, restrict access to the RESTORE command using ACL rules to prevent exploitation.
Description
RedisTimeSeries versions prior to 1.12.14 contain a vulnerability in the RESTORE command handling that allows an authenticated attacker with RESTORE permission to supply a crafted serialized payload. This triggers invalid memory access and may lead to remote code execution. The issue is patched in version 1.12.14. A workaround is to restrict RESTORE command access via ACL rules.