CVE-2026-25589VulnerabilityPublished 7 May 2026Updated 8 Sep 2026

CVE-2026-25589: redis · RedisBloom 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 25 Oct 2026, 19:02 UTC

Severity

High

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

EPSS: 1.7% chance of exploitation in 30 days – higher than 77% 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 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.6.3, 8.4.3 or 8.2.6.

Patches and advisories

github.com/RedisBloom/RedisBloom/releases/tag/v2.8.20 (opens in a new tab)

Affected software

Product	Affected	Fixed in
Bitnamiredis`pkg:bitnami/redis`Other threats	Affected >=8.0.0 <8.2.6 >=8.3.0 <8.4.3 >=8.5.0 <8.6.3	Fixed in 8.2.6 8.4.3 8.6.3

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

AI-suggested

Upgrade RedisBloom to version 2.8.20 or later, where this vulnerability is fixed. Alternatively, restrict access to the RESTORE command using Redis ACL rules to prevent unauthorized use. No other mitigation is indicated by the vendor advisory.

Description

RedisBloom versions prior to 2.8.20 contain a vulnerability in the RESTORE command handling that allows an authenticated attacker with RESTORE permission to supply crafted serialized payloads. This can cause invalid memory access and potentially lead to remote code execution. The issue is fixed in RedisBloom version 2.8.20. A workaround is to restrict RESTORE command access using ACL rules.

References

Community reviews

Loading reviews…