CVE-2025-46817VulnerabilityPublished 29 Oct 2025Updated 11 Jul 2026

Red Hat Security Advisory: redis:6 security update

Affects Red HatSource GCVE Database

Mentioned vulnerabilities

Not known to be exploited · public detection template (Nuclei) : upgrade to 6.2.20 soon.

Data as of 26 Oct 2026, 07:57 UTC

Severity

High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 3.9% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.2.20

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: evidence found.
nuclei template: Redis < 8.2.1 lua script - Integer Overflow
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade redhat/redis to 6.2.20.

Affected software

Product	Affected	Fixed in
Red Hatredhat/redis`pkg:rpm/redhat/redis`Other threats	Affected <6.2.20	Fixed in 6.2.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated Redis 6 packages (version 6.2.20-1.module+el8.10.0+...) for Red Hat Enterprise Linux 8 that fix these vulnerabilities. Users should apply the security update as detailed in the Red Hat advisory RHSA-2025:19238 and the referenced article https://access.redhat.com/articles/11258. Since this is an official fix, applying the update is the recommended remediation. No additional mitigations are specified in the advisory.

Description

Redis is an advanced key-value store. It is often referred to as a data-structure server since keys can contain strings, hashes, lists, sets, and sorted sets. For performance, Redis works with an in-memory data set. You can persist it either by dumping the data set to disk every once in a while, or by appending each command to a log. Security Fix(es): * redis: Lua library commands may lead to integer overflow and potential RCE (CVE-2025-46817) * Redis: Redis: Authenticated users can execute LUA scripts as a different user (CVE-2025-46818) * Redis: Redis is vulnerable to DoS via specially crafted LUA scripts (CVE-2025-46819) * Redis: Redis Lua Use-After-Free may lead to remote code execution (CVE-2025-49844) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities collectively allow for potential remote code execution, privilege escalation by authenticated users, and denial of service conditions in affected Redis 6 deployments on Red Hat Enterprise Linux 8. Exploitation could lead to unauthorized code execution or service disruption.

Summary

This advisory covers four distinct vulnerabilities in Redis 6 related to its Lua scripting functionality: CVE-2025-46817 involves integer overflow in Lua library commands that could lead to remote code execution; CVE-2025-46818 allows authenticated users to execute Lua scripts as different users, effectively a privilege escalation; CVE-2025-46819 permits denial of service through specially crafted Lua scripts; and CVE-2025-49844 is a Lua use-after-free vulnerability that may result in remote code execution. Red Hat has released updated Redis 6 packages for Red Hat Enterprise Linux 8 to address these vulnerabilities. The advisory rates the overall security impact as Important (high severity).

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-94Improper Control of Generation of Code ('Code Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #10OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
Architecture and Design · Refactoring
Refactor your program so that you do not have to dynamically generate code.
Architecture and Design
Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which code can be executed by your product.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V5.2.8 (opens in a new tab)
V5.2.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Leverage Executable Code in Non-Executable Files (opens in a new tab)
Manipulating User-Controlled Variables (opens in a new tab)
Code Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jul 2026, 10:59 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-190, CWE-94, CWE-416

Technical details

References

Community reviews

Related threats