惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

云风的 BLOG
云风的 BLOG
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
IT之家
IT之家
Recent Announcements
Recent Announcements
B
Blog
D
Docker
V
V2EX
GbyAI
GbyAI
L
LangChain Blog
博客园 - Franky
U
Unit 42
T
The Blog of Author Tim Ferriss
A
About on SuperTechFans
博客园 - 【当耐特】
Google DeepMind News
Google DeepMind News
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Vercel News
Vercel News
博客园_首页
D
DataBreaches.Net
人人都是产品经理
人人都是产品经理
Y
Y Combinator Blog
量子位
Blog — PlanetScale
Blog — PlanetScale
罗磊的独立博客

Sysdig Blog

Masterclass: AI is more than ChatGPT and LLMs CVE-2026-39987 update: How attackers weaponized marimo to deploy a blockchain botnet via HuggingFace Kubernetes 1.36 - New security features 5 steps to securing AI workloads Marimo OSS Python Notebook RCE: From Disclosure to Exploitation in Under 10 Hours Security briefing: March 2026 The Sysdig MCP server is now available in AWS Marketplace Risk isn’t reduced until you take action: How teams resolve issues in the cloud AI infrastructure security: Why it deserves its own category Three pillars for building effective runtime-powered cloud defense, the right way Closing the cloud security gap with runtime security Seeing risk isn’t stopping it: Why visibility alone isn’t enough TeamPCP expands: Supply chain compromise spreads from Trivy to Checkmarx GitHub Actions AI coding agents are running on your machines — Do you know what they're doing? Runtime security for AI coding agents: Protecting AI-assisted development How runtime insights power every cloud security use case CVE-2026-33017: How attackers compromised Langflow AI pipelines in 20 hours Inline Cloud Response: Accelerating AWS threat containment for SOC teams Runtime malware detection for AWS Fargate Detecting CVE-2026-3288 & CVE-2026-24512: Ingress-nginx configuration injection vulnerabilities for Kubernetes Malware detection with Sysdig Security briefing: February 2026 Leveling up Kubernetes Posture: From baselines to risk-aware admission Eliminating runtime blind spots: How CleanStart and Sysdig build continuous trust across the container lifecycle LLMjacking: From Emerging Threat to Black Market Reality Real risks live at runtime: Why CISOs must care about deep telemetry in 2026 Sysdig named a Leader in the Forrester Wave™: Cloud Native Application Protection Solutions, Q1 2026 How to run rootless containers AI-assisted cloud intrusion achieves admin access in 8 minutes Security briefing: January 2026
Understanding CVE-2025-49844: “RediShell” Critical Remote...
2025-10-07 · via Sysdig Blog

What is CVE-2025-49844?

On October 3, 2025, CVE-2025-49844 was released, describing a critical remote code execution vulnerability in the widely used open-source in-memory data store, Redis. With a CVSS score of 10.0, this issue is very severe and should be addressed quickly.

CVE-2025-49844 is a use-after-free memory corruption bug that has been present in the Redis source code for approximately 13 years. It allows an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger the use-after-free condition, and potentially achieve remote code execution. By default, Redis does not come with authentication enabled, and as a result, many developers do not enable authentication in their deployments.

This vulnerability was discovered by security researchers at Wiz and reported through Pwn2Own Berlin in May 2025, and it has been dubbed "RediShell." Redis published patches on October 3, 2025.

At the time of this publication, no exploit code is publicly available. However, proof-of-concept tools are making progress towards successful execution.

Who is affected?

CVE-2025-49844 impacts all Redis versions that include Lua scripting support.

Fixed Redis OSS/CE/Stack versions:

  • 8.2.2 and above
  • 8.0.4 and above
  • 7.4.6 and above (Stack: 7.4.0-v7 and above)
  • 7.2.11 and above (Stack: 7.2.0-v19 and above)
  • 6.2.20 and above

Fixed Redis Software (Enterprise) versions:

  • 7.22.2-12 and above
  • 7.8.6-207 and above
  • 7.4.6-272 and above
  • 7.2.4-138 and above
  • 6.4.2-131 and above

Redis Cloud customers were automatically patched and do not require action.

How does RediShell work?

RediShell exploits insufficient validation of object liveness during garbage collection in Redis's Lua scripting subsystem. Lua scripting is enabled by default in Redis and commonly used to extend functionality.

The attack enables an authenticated user to send a malicious Lua script that allows arbitrary code execution outside of the Redis Lua interpreter sandbox, in turn granting unauthorized access to the underlying host. The technical mechanism involves:

  • Memory Corruption: Crafted Lua scripts manipulate the garbage collector to free memory that is still referenced by active objects.
  • Sandbox Escape: The use-after-free condition allows code execution outside the Lua sandbox.
  • Host Access: Attackers gain native code execution on the Redis host system.

After compromising a Redis host, attackers can steal credentials, deploy malware, extract sensitive data from Redis, move laterally to other systems, or use stolen information to gain access to cloud services.

How do you detect RediShell?

With Sysdig Secure, users can leverage “RediShell Detection” in the Threat Intelligence Feed to automatically query their environments for vulnerability versions of Redis.

Users can also rely on Sysdig vulnerability management to track CVE-2025-49844, and Sysdig Sage™ for guided remediation.

Mitigation

Immediate Actions:

  • Administrators should upgrade immediately or apply temporary mitigations by restricting EVAL and EVALSHA command families using Access Control Lists (ACLs).
  • Ensure any vulnerable instances are not exposed to the Internet.
  • Prioritize patching internet-exposed instances.

Security Best Practices:

  • Restrict network access using firewalls and network policies to limit access to trusted sources.
  • Enforce strong authentication for all access to Redis instances and ensure protected-mode is enabled.
  • Run Redis with a non-root user account to limit the blast radius of potential compromise.
  • Disable Lua scripting if not required for application functionality.
  • Implement network segmentation to prevent lateral movement.
  • Avoid exposing Redis instances to the public internet entirely.

References