What is redis-rce-poc?

lyutoon/redis-rce-poc — explained in plain English

Analysis updated 2026-07-25

★ 21PythonAudience · researcherComplexity · 4/5Setup · moderate

Mindmap

mindmap
  root((repo))
    What it does
      Demonstrates Redis exploit
      Runs code remotely
      Found by AI agent
    How it works
      Exploits TDigest loading
      Triggers heap overflow
      Hijacks system function
    Tech stack
      Python 3.6+
      No third-party packages
      x86_64 Linux target
    Use cases
      Security research
      Penetration testing
      Vulnerability defense
    Audience
      Security researchers
      Penetration testers
    Setup
      Python script
      Shell test environment
      Runtime address resolution

mindmap root((repo)) What it does Demonstrates Redis exploit Runs code remotely Found by AI agent How it works Exploits TDigest loading Triggers heap overflow Hijacks system function Tech stack Python 3.6+ No third-party packages x86_64 Linux target Use cases Security research Penetration testing Vulnerability defense Audience Security researchers Penetration testers Setup Python script Shell test environment Runtime address resolution

What do people build with it?

USE CASE 1

Test your own Redis server for this vulnerability before patching.

USE CASE 2

Learn how heap overflow exploits chain together in real software.

USE CASE 3

Study how AI agents can autonomously discover security bugs.

USE CASE 4

Set up a local test environment to practice defensive security analysis.

What is it built with?

PythonRedisRedisBloom

How does it compare?

	lyutoon/redis-rce-poc	0whitedev/detranspiler	2951461586/mulerun-pool
Stars	21	21	21
Language	Python	Python	Python
Setup difficulty	moderate	hard	moderate
Complexity	4/5	4/5	3/5
Audience	researcher	developer	developer

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Requires setting up a local Redis server with the RedisBloom module on an x86_64 Linux system to safely test the exploit.

So what is it?

This repository contains a proof-of-concept exploit that demonstrates a security vulnerability in Redis, a popular open-source database. Specifically, it shows how someone with authenticated access to a Redis server running the RedisBloom module can execute arbitrary code on that server remotely. The exploit works through the Redis protocol itself, requiring no file uploads, debugger access, or direct host access. Notably, the entire exploit chain was discovered and built by an autonomous AI agent, with no manual reverse engineering involved. The underlying bug sits in how Redis loads a specific type of data structure called TDigest from saved database files. When loading this data, the software allocates memory based on one value but then trusts a different value supplied by the incoming data to check how much it can safely write. By sending a specially crafted payload, an attacker can trigger a heap overflow, writing data beyond the allocated memory. From there, the exploit chains several steps together: leaking memory addresses, reading arbitrary memory, locating key system functions, and overwriting a function pointer to redirect execution to the operating system's system() call, all running as the Redis user. The repository includes a Python script containing the full exploit and a shell script to set up a test environment. The exploit requires only Python 3.6 or later with no third-party packages, and it works against x86_64 Linux systems. It resolves all memory addresses at runtime, meaning it requires no hardcoded offsets or calibration for specific builds. The author confirmed it works against the latest Redis release at the time of testing, including versions 8.8.0 and 8.6.3. The author reported this vulnerability to Redis on June 4, 2026, but learned it had already been reported by others on December 29, 2025. As of the writing, roughly seven months after the first report, the issue remains unfixed in the latest release. The author published the exploit for educational and defensive security research purposes, and it should only be run against systems you own or are explicitly authorized to test.

Copy-paste prompts

Prompt 1

Using the redis-RCE-poc repository as a reference, explain how the TDigest heap overflow vulnerability works in RedisBloom, step by step, in plain English.

Prompt 2

Help me set up the test environment from the redis-RCE-poc repo using its shell script. Walk me through running the Python exploit safely against a local Redis instance I own.

Prompt 3

Based on the redis-RCE-poc exploit chain, what defensive measures should I implement on my Redis servers to protect against this type of remote code execution attack?

Prompt 4

Explain how an autonomous AI agent discovered this Redis exploit without manual reverse engineering. What does this mean for the future of security research?

Frequently asked questions