CriticalPublic exploitVulnerability

CVE-2025-49844

RediShell

Published Oct 3, 2025 · Updated 3 days ago

Trending this weekNot trendingOutside this week’s top 100

Mention activity · 30 days

2 mentions · peak 1 in a dayToday

CVSS9.9Critical · v3.1

EPSS82.6%100th percentile

CISA KEVNoNot listed

In the wildReported3 exploitation records in Mallory

Vendors: RedisLfprojects

IdentifiersCVE-2025-49844CWE-416 · Use After Free

RediShell is a use-after-free vulnerability in the embedded Lua scripting engine of Redis. An authenticated user with permission to execute Lua scripts can submit a specially crafted script that manipulates garbage collection, causing memory that remains referenced to be freed and subsequently reused. Successful exploitation can escape the Lua sandbox and execute arbitrary code in the Redis server process. The vulnerability affects unpatched Redis releases with Lua scripting support, including version 8.2.1; version 8.2.2 and designated maintenance releases on earlier branches contain fixes.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.

Check your exposure

Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can compromise the confidentiality, integrity, and availability of the Redis service and data accessible to its process, including cached information, session tokens, and application state. Arbitrary code execution outside the Lua sandbox can enable host compromise and further lateral movement, subject to the Redis process's operating-system privileges and deployment isolation. It does not inherently guarantee administrative or root privileges.

Mitigation

If you can’t patch tonight, do this now.

If an upgrade is not immediately possible, prevent untrusted users from executing Lua scripts by applying Redis ACL restrictions to EVAL and EVALSHA. Review other available Lua execution entry points and deny unnecessary scripting permissions. Enforce authentication and restrict Redis network access to trusted clients and necessary cluster nodes using firewall rules, private networking, or VPN access. Authentication and network restrictions reduce exposure but do not protect against an authorized user who retains permission to execute malicious scripts. For Carbon Black EDR deployments, apply the vendor's command-disabling workaround on every applicable node; containerized installations require the vendor upgrade because manual configuration changes do not persist across service restarts.

Remediation

Patch, then assume compromise.

Upgrade Redis OSS/Community Edition to a fixed release on the applicable branch: 8.2.2, 8.0.4, 7.4.6, or 7.2.11, or a subsequent patched release. Fixed Redis Stack releases include 7.4.0-v7 and 7.2.0-v19. Fixed Redis Software releases include 7.22.2-12, 7.8.6-207, 7.4.6-272, 7.2.4-138, and 6.4.2-131. For products bundling Redis, apply the product vendor's supported security update rather than independently replacing the bundled component. Carbon Black EDR Server 7.9.0 addresses exposure by disabling Lua scripting commands, not by replacing Redis with an upstream-patched version.

Public exploits

Exploits

11 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →

CVE-2025-49844This repository contains a Python-based exploit for CVE-2025-49844, a Use-After-Free (UAF) vulnerability in the Redis Lua interpreter. The main exploit logic resides in 'redis_exploit.py', which implements a multi-stage attack: it connects to a target Redis server, checks for vulnerability, detects architecture, performs heap spraying, creates UAF objects, leaks memory to bypass ASLR, constructs a ROP chain to bypass DEP/NX, and finally executes arbitrary shellcode. The exploit can establish a reverse shell to the attacker's machine and optionally create a persistent backdoor. The exploit is configurable via command-line arguments for target host, port, authentication, and reverse shell parameters. The README provides detailed usage instructions, supported Redis versions, and detection guidance. The repository is operational and suitable for real-world exploitation of vulnerable Redis instances.Yuri08loveElaina · Disclosed Oct 9, 2025 · python · networkOperational CVE-2025-49844This repository is a small single-file proof-of-concept exploit for CVE-2025-49844 targeting Redis 8.2.1. The structure is minimal: one main Python exploit script (CVE-2025-49844.py), a short README, and a requirements file. The Python script is the clear entry point and contains the full exploit chain, target metadata structures, shellcode generation logic, CLI handling, and execution flow. The exploit is not a scanner or detector; it is an active RCE PoC. Its stated purpose is to exploit a Redis Lua use-after-free condition and deliver a reverse shell. The code imports the redis Python client to communicate with the target Redis server and uses iced-x86 to dynamically assemble native x86-64 shellcode. The shellcode builder includes a reverse-shell routine that prepares a sockaddr structure from an operator-supplied IPv4 address and port, creates a TCP socket, connects back to the listener, duplicates file descriptors, and executes /bin/sh. The code also references low-level runtime addresses such as luaAlloc, mprotect, and pthread_create, indicating the exploit performs memory corruption and control-flow pivoting rather than simple command injection. The command-line interface supports specifying the Redis target host and port (-H/-P) and the callback listener host and port (-l/-p). Defaults are 127.0.0.1:6379 for Redis and 127.0.0.1:4444 for the reverse shell. The README confirms the repository’s purpose as a reverse-shell PoC and points to an original upstream PoC. Overall, this is an operational exploit PoC for remote network-based exploitation of a vulnerable Redis instance. It contains a real payload, requires a vulnerable target and a reachable attacker listener, and is designed to achieve code execution with a reverse shell rather than merely demonstrating a crash or checking exposure.Cilectiy · Disclosed Mar 13, 2026 · python · networkOperational CVE-2025-49844This repository is a small multi-file exploit lab centered on Redis vulnerabilities, primarily CVE-2025-49844 ('RediShell') and secondarily CVE-2025-62507. It is not part of a known exploit framework. The structure includes several Python exploit variants, one Node.js PoC, a standalone Lua repro script, a helper script for brute-forcing a PIE base address, and Docker artifacts for spinning up an intentionally insecure Redis test environment. The Redis 2025-49844 content focuses on Lua interpreter abuse via EVAL. Multiple files build nearly identical Lua heap-spray / re-entrant garbage-collection scripts using newproxy, loadstring, collectgarbage, and repeated allocations to try to trigger a use-after-free and restore restricted functions such as os.execute or print. The more advanced Python variants analyze a local redis-server ELF with pwntools, compute symbol offsets such as luaEngineInitEngine or luaopen_base, and then send raw RESP EVAL requests to a remote Redis instance. Some variants proceed to a second stage that attempts command execution with a hardcoded bash reverse shell to an attacker-supplied IP and port. The helper script find_base.py tries to brute-force the PIE base address by repeatedly sending EVAL payloads and checking for a successful RESP bulk-string response. The Node.js file POC.js is a more feature-rich Redis client/PoC wrapper. It implements RESP encoding/parsing manually over a TCP socket, supports authentication, and exposes modes such as check/basic/sandbox/advanced/custom/sh/all. Based on the visible code and README, it is intended to test connectivity, verify Lua availability, attempt simplified UAF/sandbox-escape behaviors, and optionally run a shell-oriented payload. This makes the repository operational rather than a pure readme or detector. The Dockerfile and docker-compose.yml create a lab Redis instance with protected-mode disabled, bind 0.0.0.0, and expose Redis externally. This is clearly for local testing and makes the target reachable on host port 6380. A separate file, CVE-2025-62507_Crash_Working_PoC_BufferOverflow.py, is the clearest working exploit artifact in the repo. It connects to Redis on TCP/6379, creates a stream/consumer group with XGROUP CREATE mystream mygroup 0-0 MKSTREAM, then sends an XACKDEL command with an excessive number of crafted stream IDs to overflow a fixed-length vector and crash the server. This is a network-reachable crash PoC for Redis and appears more reliable than the RediShell RCE attempts. Overall, the repository’s purpose is exploratory exploit development against Redis: testing whether CVE-2025-49844 can yield sandbox escape/RCE and documenting that the authors more reliably achieved crashes than code execution, while also including a separate working crash PoC for CVE-2025-62507.open-flaw · Disclosed Apr 6, 2026 · python · javascript · network · webOperational CVE-2025-49844This repository is a mixed Redis exploit lab focused mainly on CVE-2025-49844 ('RediShell') with an additional crash PoC for CVE-2025-62507. It is not tied to a major exploit framework. The structure includes multiple iterative Python exploit attempts, one JavaScript PoC, a Lua repro script, and Docker artifacts for standing up an intentionally insecure Redis test instance. Repository layout and purpose: - Dockerfile + docker-compose.yml: build a Redis 7.2.0 lab container, disable protected mode, bind on 0.0.0.0, and expose Redis on host port 6380. - exploit_poc.py and POC.js: general-purpose PoC clients that connect to Redis, check version/Lua availability, and run staged tests such as basic UAF triggering, sandbox-boundary checks, and more advanced corruption attempts. - exploit.py, exploit_poc_another_one.py, exploit_poc_another_attempt.py, exploit_poc_one_more_attempt.py: more aggressive/manual exploitation attempts for CVE-2025-49844. These scripts craft Lua heap-spray / GC re-entrancy payloads, compute target function addresses from a local redis-server ELF and a supplied base address, then try to restore blocked Lua functions (print, os.execute) or directly execute a reverse shell. - find_base.py: helper script intended to brute-force the PIE base address by repeatedly sending EVAL payloads and checking for a success indicator. - korean_puzzle_piece.lua: standalone Lua repro script for the GC-during-parsing condition. - CVE-2025-62507_Crash_Working_PoC_BufferOverflow.py: separate PoC targeting Redis XACKDEL with an oversized IDS vector to trigger a stack overflow/crash. - README.md: candid notes indicating the author could reproduce crashes but not reliable code execution for CVE-2025-49844, and that CVE-2025-62507 appeared more reliably crashable. Main exploit capabilities: 1. Network interaction with Redis over TCP, usually on localhost:6379 or docker-mapped localhost:6380. 2. Raw RESP command construction and EVAL delivery of attacker-controlled Lua scripts. 3. Lua GC re-entrancy/UAF triggering via newproxy, __gc metamethods, collectgarbage('collect'), loadstring, and heap churn/spraying. 4. Symbol-based targeting of redis-server internals such as luaEngineInitEngine, luaopen_base, and luaopen_os using pwntools ELF parsing and user-supplied base addresses. 5. Post-corruption command execution attempts using os.execute and a bash reverse shell to /dev/tcp/<attacker-ip>/<attacker-port>. 6. Crash-oriented exploitation of XACKDEL by sending more IDs than the static vector length supports. Assessment of exploit quality: - The repository contains real exploit-oriented code, not just documentation. - However, the README and code comments show the CVE-2025-49844 RCE path is experimental and unstable; much of it is best treated as PoC/operational research code rather than a reliable weaponized exploit. - The CVE-2025-62507 script is more straightforward and appears intended primarily to demonstrate a crash/overflow condition rather than full RCE. Overall, this repository is best characterized as an exploit research collection for Redis vulnerabilities, combining lab setup, vulnerability checks, crash reproducers, and several iterative attempts at turning a Redis Lua interpreter memory corruption bug into sandbox escape and remote code execution.dajneem23 · Disclosed Apr 6, 2026 · python · javascript · network · webOperational CVE-2025-49844This repository is a standalone Python exploit for CVE-2025-49844 ('RediShell'), a Redis Lua scripting use-after-free that can lead to authenticated remote code execution. The repository is minimal: one main exploit script (CVE-2025-49844.py), a README describing affected versions and limitations, and a requirements file listing redis and iced-x86 dependencies. The exploit script is not a scanner or detector; it is a real exploitation tool. It accepts target connection parameters and a command to run, connects to a Redis server using redis-py, performs a vulnerability/build suitability check unless --force is used, then constructs multiple exploit stages. The code defines numerous low-level structures (for example CClosure and Proto), target/build metadata, shellcode context, and target-specific modules/protocols. It uses these to craft malicious Lua-side data structures, fake objects, encoded payload blobs ('megabin'), and a pivot/JOP chain. The inclusion of iced-x86 indicates the exploit dynamically assembles or manipulates machine instructions for shellcode/pivot generation. Operational flow visible in the script includes: parsing CLI arguments; optionally checking whether the target appears vulnerable; generating shellcode for a user-supplied command; preparing exploit state with resolved addresses such as redis_base, luaAlloc, mprotect, and pthread_create; building a target-specific pivot payload; flushing Redis scripts; and finally invoking client.eval(...) with crafted Lua content to trigger the corrupted upvalue path and transfer execution into shellcode. The script logs success/failure states and reports 'Exploit completed' on success. Targeting is broad at the version-check level but narrow in practical exploitability. The README states affected Redis branches include 6.2, 7.2, 7.4, 8.0, and 8.2 before their respective fixes, but the actual exploit is only said to work reliably against redis:8.2.1-alpine (build ID f5a80511e802827d) and redis:8.2.1-bookworm (build ID fcae35583392417f). This strongly suggests dependence on exact binary layout, offsets, and gadgets rather than generic version-only exploitation. Primary attack vector is network-based against an exposed Redis service. The key fingerprintable target interface is the Redis TCP service specified by host and port arguments, with exploitation performed through Lua scripting commands such as EVAL and script cache manipulation. The end result is arbitrary command execution on the Redis host, but the README notes command output is not returned to the operator.cc3305 · Disclosed Jun 16, 2026 · python · markdown · network · webOperational redis_exploitThis repository provides a proof-of-concept (PoC) exploit for CVE-2025-49844 (RediShell), a critical use-after-free vulnerability in the Redis Lua interpreter. The main exploit logic is implemented in 'exploit_poc.py', a Python script that connects to a target Redis server (default localhost:6379, configurable via command-line), checks for Lua scripting support, and executes crafted Lua scripts to trigger the vulnerability. The script supports multiple modes: basic UAF trigger, sandbox escape attempts, and advanced memory corruption demonstration. The payloads are Lua scripts executed via the Redis EVAL command. The repository includes a Dockerfile and docker-compose.yml to set up a vulnerable Redis 7.2.0 instance with insecure settings (protected mode off, open to the network) for testing. No hardcoded IPs or domains are present, but the exploit targets TCP endpoints (default Redis port). The repository is structured for educational and authorized testing purposes, with clear warnings against unauthorized use. The exploit is a PoC and does not provide a weaponized or fully automated attack chain.ksnnd32 · Disclosed Apr 13, 2019 · python · docker · networkPoC CVE-2025-49844This repository contains a Python exploit (redis_exploit.py) targeting CVE-2025-49844, a use-after-free (UAF) vulnerability in Redis. The exploit connects to a specified Redis server (default localhost:6379), checks for vulnerable versions (7.2 < 7.2.11, 7.4 < 7.4.6, 8.0 < 8.0.4, 8.2 < 8.2.2), and requires Lua scripting to be enabled. It performs heap spraying, creates UAF objects via Lua scripts, triggers the UAF, leaks memory, locates ROP gadgets, builds and executes shellcode, and can establish a reverse shell to an attacker-specified host and port. The exploit is operational and provides remote code execution and persistence capabilities. The repository includes a README with usage instructions, a requirements.txt for dependencies, and a license file. No hardcoded external endpoints are present; the exploit targets user-specified Redis instances over the network.Zain3311 · Disclosed Apr 6, 2022 · python · networkPoC CVE-2025-49844This repository contains a proof-of-concept exploit for CVE-2025-49844, a use-after-free vulnerability in the Lua parser embedded in Redis versions up to 8.2.1. The exploit is implemented as a Lua script (CVE-2025-49844.lua) that repeatedly invokes the Lua 'loadstring' function with a specially crafted chunk name whose garbage collection is triggered during parsing. This can cause the Redis process to crash or, in some cases, allow remote code execution. The README provides detailed background, usage instructions (using redis-cli to execute the script against a local or network-accessible Redis instance), and mitigation advice. The exploit targets the Redis server's Lua scripting feature and requires network access to the Redis service, typically on TCP port 6379. The repository is structured simply, with the main exploit script and a comprehensive README.dwisiswant0 · Disclosed Oct 7, 2025 · lua · markdown · networkPoC redis_exploitThis repository provides a practical lab and proof-of-concept (PoC) exploit for CVE-2025-49844 (RediShell), a critical use-after-free vulnerability in the Redis Lua interpreter that can lead to remote code execution. The repository includes a Dockerfile and docker-compose.yml to set up a vulnerable Redis 7.2.0 instance with intentionally insecure settings (protected-mode disabled, bound to 0.0.0.0, port 6379 exposed as 6380). The main exploit logic resides in 'exploit_poc.py', a Python script that connects to the Redis instance, checks for the vulnerability, and executes various Lua scripts to trigger the UAF, test sandbox boundaries, and demonstrate memory corruption. The exploit is interactive and supports multiple modes (check, basic, sandbox, advanced, all), with optional authentication. The README.md provides detailed setup, usage instructions, and security recommendations. The exploit is a proof-of-concept and does not include a weaponized payload, but demonstrates the core vulnerability and its potential impact. No hardcoded IPs or domains are present; the default target is localhost:6380 as configured in the lab. The repository is structured for educational and testing purposes, not for real-world attacks.raminfp · Disclosed Oct 7, 2025 · python · docker · networkPoC cve-2025-49844This repository is a proof-of-concept exploit for CVE-2025-49844 (RediShell), targeting the x86-64 Linux build of Redis 8.2.1 as distributed in the official Docker image. The repository contains 10 files, with the main exploit logic implemented in 'main.py' (37kB) and a demonstration script in 'demonstration.py'. The exploit leverages a vulnerability in Redis's Lua scripting engine to inject and execute arbitrary x86-64 shellcode. It supports two main capabilities: executing arbitrary shell commands on the Redis server, or establishing a reverse shell to an attacker-specified IP and port. The exploit is delivered via the Redis protocol (TCP port 6379), and the default configuration targets a local Redis instance for testing. The repository includes Docker and Compose files to facilitate local testing with the correct Redis version. The exploit is a functional proof-of-concept, not weaponized, and is intended for research and demonstration purposes.saneki · Disclosed Oct 31, 2025 · python · networkPoC CVE-2025-49844-RediShell-AI-made-RevshellThis repository contains a proof-of-concept exploit for CVE-2025-49844 (RediShell), targeting specific vulnerable versions of Redis. The main file, exploit.py, is a Python script that connects to a Redis instance, checks if it is vulnerable based on its version, and then delivers a custom 64-bit shellcode payload via a Lua script. The payload is designed to open a reverse shell from the Redis server to an attacker-controlled machine, granting remote command execution. The exploit requires the attacker to specify their own IP and port to receive the shell. The README notes that this is an AI-generated, untested PoC, and the exploit is based on a conceptual approach. The repository structure is simple, with a single exploit script and a README. The exploit leverages the Redis Lua scripting engine and memory manipulation to hijack execution flow and run arbitrary shellcode.Network-Sec · Disclosed Nov 11, 2025 · python · networkPoC

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

LfprojectsValkeyapplication

RedisRedisapplication

External references

References

MITRE CVEcve.org · CVE-2025-49844 NVDnvd.nist.gov/vuln/detail/CVE-2025-49844 MITRE CWE · CWE-416Use After Free Patchgithub.com/redis/redis/commit/d5728cb5795c966c5b5b1e0f0ac576a7e69af539 Third Party Advisoryopenwall.com/lists/oss-security/2025/10/07/2 Third Party Advisorygithub.com/redis/redis/security/advisories/GHSA-4789-qfc9-5f9q Release Notesgithub.com/redis/redis/releases/tag/8.2.2 github.comgithub.com/lastvocher/redis-CVE-2025-49844

Activity feed

Recent activity

244 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →

tenable nessus pluginsNews · Oct 27, 2026Unity Linux 20.1050a / 20.1060a / 20.1070a Security Update: re... | Tenable®An authenticated remote code execution vulnerability in Redis Lua scripting. A crafted Lua script can manipulate garbage collection to trigger a use-after-free. The advisory states that all Redis versions supporting Lua scripting through 8.2.1 are affected, with a fix in 8.2.2. This reference covers the affected Redis package on Unity Linux 20.1050a, 20.1060a, and 20.1070a under advisory UTSA-2026-146134. The listed CVSS v3 base score is 8.8. Nessus detects exposure using the application's self-reported version rather than testing exploitation. Update the Redis package; alternatively, use ACLs to restrict EVAL and EVALSHA to prevent Lua script execution.Read more ↗nuclei templates pull requestsNews · Oct 15, 2026fix(redis): fix false positives for Redis Lua CVEs by checking branch-specific versions by Wandering-y · Pull Request #17427 · projectdiscovery/nuclei-templatesA Redis Lua vulnerability referenced in a change addressing false-positive vulnerability detection across version branches. The excerpt does not describe its technical mechanism, impact, or explicitly mapped affected versions.Read more ↗tenable nessus pluginsNews · Aug 25, 2026Redis < 6.2.20 / 7.0.x < 7.2.11 / 7.4.x < 7.4.6 / 8.0.x < 8.0.... | Tenable®A specific vulnerability in Redis Server associated with CWE-416 (use-after-free).Read more ↗metasploit pull requestsNews · Jul 24, 2026Redishell CVE 2025 49844 scanner by X-croot · Pull Request #21707 · rapid7/metasploit-framework · GitHubA Redis Lua use-after-free vulnerability, referred to as RediShell, affecting unpatched Redis branches when Lua EVAL functionality is reachable.Read more ↗

+19 more in the timeline. Sign up to see them

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.

Check your exposure

Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.

Start Free Trial Open in App ↗

Exposure mappingQuery your assets running an affected version, and investigate the blast radius.

Threat actor evidenceEvery report linking this CVE to a named adversary.

Associated malware3Malware families linked to this CVE, with evidence and IOCs.

Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.

Social activity169Community discussion across Reddit, Mastodon, and other social sources.