CVE-2025-46819 | Redis is vulnerable to DoS via specially crafted LUA scripts

Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted LUA script to read out-of-bound data or crash the server and subsequent denial of service. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to block a script by restricting both the EVAL and FUNCTION command families.

Published: 2025-10-03 Last update: 2026-01-27 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-46819 is rated Moderate Risk (56.5/100): CVSS Medium severity, with high exploitation likelihood (EPSS 7.83%, 92th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-46819

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-08 8.77% 7.83% -0.94%
2 2026-05-24 9.34% 8.77% -0.58%
3 2026-05-22 — 9.34% —

Full EPSS history (19 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-46819

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 3.1 MEDIUM
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.0 5.2 [email protected]
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.2 [email protected]

Weakness enumeration for CVE-2025-46819

OS Trackers for CVE-2025-46819

vendor priority summary link
alpine — CVE-2025-46819: 3 source package rows (redict, redis, valkey); 104 state rows across 8 repos (3.19-main, 3.20-main, 3.21-main, 3.22-community, 3.22-main, 3.23-community, edge-community, edge-main); fixed 19, open 85. https://security.alpinelinux.org/vuln/CVE-2025-46819
debian not yet assigned CVE-2025-46819 not yet assigned priority: Debian including 3 source packages (redict, redis, valkey), 10 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 10. https://security-tracker.debian.org/tracker/CVE-2025-46819
redhat medium — https://access.redhat.com/security/cve/CVE-2025-46819
suse critical CVE-2025-46819 severity critical: SUSE including 31 source package names (8.0.6-2.44:valkey-8.0.6-150600.13.17.1, docker-27.5.1_ce-slfo.1.1_2.1, …), 111 product×package rows across 51 product lines (Container private-registry/harbor-valkey, Image SL-Micro-Azure, … (51 product lines)): Fixed 102, Known Not Affected 6, First Fixed 3. https://www.suse.com/security/cve/CVE-2025-46819/
ubuntu medium CVE-2025-46819 medium priority: Ubuntu including 3 source packages (redict, redis, valkey), 19 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needed 7, released 5, DNE 3, ignored 2, needs-triage 2. https://ubuntu.com/security/CVE-2025-46819

Affected software / configurations for CVE-2025-46819

Vendor Product Version Raw CPE
redis redis < 6.2.20 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 7.0, < 7.2.11 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 7.4.0, < 7.4.6 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 8.0.0, < 8.0.4 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*
redis redis >= 8.2.0, < 8.2.2 cpe:2.3:a:redis:redis:*:*:*:*:*:*:*:*

References for CVE-2025-46819

cvelogic Threat Intelligence