CVE Watchtower

CVE-2026-62356RedisBloom >= 2.0.0, Integer Overflow or Wraparound

NVD

Vulnerability Summary

Impact An authenticated user may trigger a heap out-of-bounds write in RedisBloom by loading a specially crafted Count-Min Sketch (CMSketch) object, for example via the RESTORE command or a crafted RDB file. Successful exploitation could result in denial of service or, potentially, remote code execution in the context of the Redis server process. The issue affects Redis deployments running vulnerable versions of RedisBloom. Workarounds Users unable to immediately upgrade can reduce exposure by restricting access to commands and workflows capable of loading serialized Redis data, including RESTORE and RDB import mechanisms. Deployments should ensure that only trusted users are permitted to create or load RedisBloom CMSketch objects. Applying ACL restrictions to prevent untrusted users from executing data restoration operations may mitigate the risk of exploitation.
Severity Level
HIGH(7.5)
Published Date
Aug 17, 2026
Last Modified
Aug 17, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes the resulting value will always be larger than the original.
The product writes data past the end, or before the beginning, of the intended buffer.
CVSS v4.0 Base Metrics — Score 7.5
CVSS:4.0/AV:A/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Attack VectorAdjacent
Attack ComplexityHigh
Attack RequirementsNone
Privileges RequiredLow
User InteractionNone
Confidentiality (Vulnerable System)High
Integrity (Vulnerable System)High
Availability (Vulnerable System)High
Confidentiality (Subsequent System)None
Integrity (Subsequent System)None
Availability (Subsequent System)None

Affected & Patched Versions

Affected Versions
  • RedisBloom >= 2.0.0, <= 2.8.23
  • Redis OSS >= 8.0.0, <= 8.0.8
  • Redis OSS >= 8.2.0, <= 8.2.15
  • Redis OSS >= 8.4.0, <= 8.4.8
  • Redis OSS >= 8.6.0, <= 8.6.5
  • Redis OSS >= 8.8.0, <= 8.8.1
  • Redis OSS = 8.10.0
  • Redis Software >= 7.2.4-52, <= 7.2.4-153
  • Redis Software >= 7.4.2-54, <= 7.4.6-279
  • Redis Software >= 7.8.2-34, <= 7.8.6-260
  • Redis Software >= 7.22.0-95, <= 7.22.2-116
  • Redis Software >= 8.0.2-17, <= 8.0.18-36
Patched Versions
  • RedisBloom 2.8.24, 2.6.32, 2.4.27
  • Redis OSS 8.2.9
  • Redis OSS 8.4.6
  • Redis OSS 8.6.6
  • Redis OSS 8.8.2
  • Redis OSS 8.10.1
  • Redis Software 7.2.4-154
  • Redis Software 7.4.6-280
  • Redis Software 7.8.6-263
  • Redis Software 7.22.2-133
  • Redis Software 8.0.20-19

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run RedisBloom >= 2.0.0, and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Aug 17, 2026Published
  • Aug 17, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new RedisBloom >= 2.0.0, CVEsYou are reading CVE-2026-62356. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 17, 2026 20:00 UTC