Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-62356-POC — RedisBloom CMSketch RDB-load integer overflow (CVE-2026-62356) — non-weaponized PoC: deterministic crash/DoS reproducer, analysis & version matrix | Kitploit
Tools/GitHubGitHub/zsy-arch/cve-2026-62356-poc
Defensive ToolsMemory ForensicsVulnerability AnalysisExploitationBinary AnalysisDatabase Security
GitHubzsy-arch/cve-2026-62356-poc

CVE-2026-62356-POC

RedisBloom CMSketch RDB-load integer overflow (CVE-2026-62356) — non-weaponized PoC: deterministic crash/DoS reproducer, analysis & version matrix

View Repository
127 days agoNot yet reviewed
Share

English | 中文

CVE-2026-62356 — RedisBloom CMSketch RDB Load Integer Overflow (PoC)

An integer-overflow vulnerability in RedisBloom's Count-Min Sketch (CMSketch) RDB deserialization path. An authenticated Redis client can load a specially crafted CMSketch object (via RESTORE or a crafted RDB file) whose declared dimensions overflow the expected-buffer-length computation, causing an undersized heap buffer to be accepted. Any subsequent CMS command (CMS.QUERY / CMS.INCRBY / CMS.INFO) then indexes far out of bounds — a crash (DoS) at minimum, and, per the upstream advisory, potentially remote code execution in the context of the Redis server process.

This repository contains a non-weaponized proof of concept: a deterministic crash/DoS reproducer plus supporting analysis tooling. It does not contain a working RCE exploit chain.

Advisory & Attribution

CVECVE-2026-62356
GHSAGHSA-q5p6-hwxh-c23h
Reporter (to upstream)josephsurin
CWECWE-190 (Integer Overflow), CWE-787 (OOB Write)
Published2026-08-17
CVSSHigh (CVSS:4.0 AV:A/AC:H/PR:L/…)

Affected versions (per upstream advisory): Redis OSS 8.0.0–8.0.8, 8.2.0–8.2.15, 8.4.0–8.4.8, 8.6.0–8.6.5, 8.8.0–8.8.1, 8.10.0; RedisBloom 2.0.0–2.8.23. Fixed in: Redis 8.8.2 / RedisBloom 2.8.24 (and corresponding backports).

This repository is an independent reproduction. Credit for discovery and responsible disclosure belongs to the upstream reporter named above.

Root Cause (summary)

CMSRdbLoad reads attacker-controlled width / depth from the serialized object and computes the expected array length as 4 * width * depth in 64-bit arithmetic without an overflow check. Because the payload length check compares against this wrapped product, a payload whose dimensions make the product wrap (e.g. width = depth = 2^32 → product = 2^66 mod 2^64 = 0) passes validation with an empty or undersized array buffer, while the in-memory sketch retains the huge declared dimensions.

Every later cell access is:

loc = (MurmurHash2(item, seed = row) % width) + row * width;
array[loc] ...            // array is the undersized buffer; loc is huge

so any CMS command dereferences array + 4*loc — an out-of-bounds access at an attacker-influenceable offset (the hash is computable offline, MurmurHash2 with known seeds). The full analysis is in docs/ANALYSIS.md.

Reproduction

Environment: Docker, any host platform (use --platform linux/amd64 on ARM Macs).

# 1) start a vulnerable lab (redis:8.8.1, bundled pre-fix RedisBloom, port 6381)
bash poc/setup_lab.sh

# 2) inject the poisoned CMSketch object and trigger the crash
python3 poc/cms_overflow_crash.py --port 6381
#    -> CMS.QUERY gets no reply; subsequent PING fails: SIGSEGV confirmed
#    -> server log shows "Accessing address: 0x..." inside CMS_Query/CMS_IncrBy

# 3) (optional) verify persistence: poisoned key survives restart via RDB
docker restart cve-2026-62356-lab
#    any CMS.QUERY on the key crashes the server again — persistent DoS

# 4) cleanup / recover
python3 poc/cms_overflow_crash.py --port 6381 --cleanup

Expected output (step 2):

[*] sanitize-dump-payload: +OK
[*] injecting poisoned CMS key (width=depth=2^32, array=NULL)...
[*] RESTORE -> +OK
[*] predicted fault address (depth=1): 0x...
[*] triggering via CMS.QUERY ...
[*] CMS.QUERY -> (no reply / crashed)
[*] PING -> (no reply / crashed)

Repository Layout

poc/
  setup_lab.sh          start a pinned vulnerable redis:8.8.1 container
  cms_overflow_crash.py crash/DoS reproducer (inject + trigger + cleanup)
  cmslib.py             shared RESP client / payload builder helpers
  leak_base.py          analysis tool: crash-free heap-layout inference (read-only)
  mkwin2.c              analysis tool: MurmurHash2 preimage table generator (offline)
  mm2_preimage.c        analysis tool: single-hash MurmurHash2 preimage solver (offline)
docs/
  ANALYSIS.md           detailed vulnerability analysis (English)

Mitigation

  1. Upgrade to Redis 8.8.2+ / RedisBloom 2.8.24+ (or the backported release for your branch — see the GHSA advisory for the full fixed-version matrix).
  2. If you cannot upgrade: restrict RESTORE, MIGRATE, DEBUG and RDB-file ingestion to trusted users via ACLs; treat any serialized-data import path (replication, --rdb preload, backup restore) as equally sensitive.

Legal Notice & Disclaimer

This repository is published for educational and defensive research purposes only, to help operators understand, detect, and patch the vulnerability.

  • Testing may only be performed on systems you own or are explicitly and in writing authorized to test. Unauthorized access to computer systems is illegal in most jurisdictions.
  • The PoC is deliberately non-weaponized: it demonstrates a crash (denial of service) and the underlying memory-safety failure. It does not include a remote-code-execution exploit chain, and no such chain will be added.
  • The code is provided "AS IS", without warranty of any kind. The authors are not liable for any damage arising from the use or misuse of this material.
  • If you believe your use of this information may be unlawful in your jurisdiction, do not use it.

Discovery and disclosure credit: josephsurin (upstream reporter). This repository's reproduction and analysis are independent work.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    755
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    510
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    415
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    343
  • 5

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    259
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    258

Explore all tools

Browse our collection of tools

View all tools →