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.