CVE-2025-46819: Redis is vulnerable to DoS via specially crafted LUA scripts
Noroxi assessment
Priority: Monitor (action score 28/100)
- A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1% (FIRST EPSS); higher than 65.4% of all records.
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: redis redis 8.2.2; azl3 valkey 8.0.4-1 on Azure Linux 3.0 8.0.6-1.
Low priority for now. Upgrade to redis redis 8.2.2; azl3 valkey 8.0.4-1 on Azure Linux 3.0 8.0.6-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- ALSA-2025:19237
- ALSA-2025:19238
- ALSA-2025:19345
- ALSA-2025:19675
- ALSA-2025:20926
- ALSA-2025:20955
- ALSA-2025:21916
- ALSA-2025:21936
- DLA-4325-1
- DSA-6020-1
- DSA-6022-1
- openSUSE-SU-2025:15600-1
- openSUSE-SU-2025:15604-1
- openSUSE-SU-2025:20121-1
- openSUSE-SU-2026:20003-1
- RHSA-2025:19237
- RHSA-2025:19238
- RHSA-2025:19345
- RHSA-2025:19675
- RHSA-2025:20926
- Published
- Oct 3, 2025
- Updated
- Oct 19, 2026
- EPSS
- 1.0% · 65th percentile
- CWE
- CWE-190
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.1
- CNA · GitHub_M
- 6.3
- 0.8 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redis | redis | cpe:2.3:a:redis:redis |
Using redis? Add it to your stack and be the first to know about CVEs like this one. (Redis)
Is Redis on your server exposed to the internet?
The free port scanner finds the open ports on your server and matches the service versions it can read against known vulnerabilities. No account needed.
Run a port scanAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redis redisbefore 6.2.20
- redis redis7.0 and later · before 7.2.11
- redis redis7.4.0 and later · before 7.4.6
- redis redis8.0.0 and later · before 8.0.4
- redis redis8.2.0 and later · before 8.2.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
redis redis
- < 8.2.2affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | valkey | before 8.0.6-1.el10_0 | 8.0.6-1.el10_0 |
| AlmaLinux:10 | valkey | before 8.0.6-2.el10_1 | 8.0.6-2.el10_1 |
| AlmaLinux:10 | valkey-devel | before 8.0.6-2.el10_1 | 8.0.6-2.el10_1 |
| AlmaLinux:10 | valkey-devel | before 8.0.6-1.el10_0 | 8.0.6-1.el10_0 |
| AlmaLinux:8 | redis | before 6.2.20-1.module_el8.10.0+4056+739731b0 | 6.2.20-1.module_el8.10.0+4056+739731b0 |
| AlmaLinux:8 | redis-devel | before 6.2.20-1.module_el8.10.0+4056+739731b0 | 6.2.20-1.module_el8.10.0+4056+739731b0 |
| AlmaLinux:8 | redis-doc | before 6.2.20-1.module_el8.10.0+4056+739731b0 | 6.2.20-1.module_el8.10.0+4056+739731b0 |
| AlmaLinux:9 | redis | before 7.2.11-1.module_el9.6.0+188+92104ce8 | 7.2.11-1.module_el9.6.0+188+92104ce8 |
| AlmaLinux:9 | redis | before 6.2.20-1.el9_6 | 6.2.20-1.el9_6 |
| AlmaLinux:9 | redis | before 6.2.20-2.el9_7 | 6.2.20-2.el9_7 |
| AlmaLinux:9 | redis-devel | before 6.2.20-1.el9_6 | 6.2.20-1.el9_6 |
| AlmaLinux:9 | redis-devel | before 6.2.20-2.el9_7 | 6.2.20-2.el9_7 |
| AlmaLinux:9 | redis-devel | before 7.2.11-1.module_el9.6.0+188+92104ce8 | 7.2.11-1.module_el9.6.0+188+92104ce8 |
| AlmaLinux:9 | redis-doc | before 6.2.20-1.el9_6 | 6.2.20-1.el9_6 |
| AlmaLinux:9 | redis-doc | before 6.2.20-2.el9_7 | 6.2.20-2.el9_7 |
| AlmaLinux:9 | redis-doc | before 7.2.11-1.module_el9.6.0+188+92104ce8 | 7.2.11-1.module_el9.6.0+188+92104ce8 |
| AlmaLinux:9 | valkey | before 8.0.6-2.el9_7 | 8.0.6-2.el9_7 |
| AlmaLinux:9 | valkey-devel | before 8.0.6-2.el9_7 | 8.0.6-2.el9_7 |
| Alpine:v3.20 | valkey | before 7.2.11-r0 | 7.2.11-r0 |
| Alpine:v3.21 | redis | from 7.0 · before 7.2.11-r0 | 7.2.11-r0 |
| Alpine:v3.22 | redict | before 7.3.6-r0 | 7.3.6-r0 |
| Alpine:v3.22 | redis | from 7.0 · before 8.0.4-r0 | 8.0.4-r0 |
| Alpine:v3.22 | valkey | before 8.1.4-r0 | 8.1.4-r0 |
| Alpine:v3.23 | redis | from 7.0 · before 8.2.2-r0 | 8.2.2-r0 |
+66
Same product
redis: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0543It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific) Lua sandbox escapeKEV100Now
- CVE-2025-49844Redis Lua Use-After-Free may lead to remote code execution64This week
- CVE-2023-36824Heap overflow in COMMAND GETKEYS and ACL evaluation in Redis58Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-46817Oct 3, 2025 · Lua library commands may lead to integer overflow and potential RCE36Monitor
- ← EarlierCVE-2025-46818Oct 3, 2025 · Redis: Authenticated users can execute LUA scripts as a different user29Monitor
- Later →CVE-2025-62507Nov 4, 2025 · Redis: Bug in XACKDEL may lead to stack overflow and potential RCE32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| redis redis | 8.2.2 · description | Vendor (CNA) |
| azl3 valkey 8.0.4-1 on Azure Linux 3.0 | 8.0.6-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:redis | 6.2.20-1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:redis-devel | 6.2.20-1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:redis-doc | 6.2.20-1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:valkey | 8.0.6-1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:valkey-devel | 8.0.6-1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| alpine:redict | 7.3.6-r0 · Alpine:v3.22 | Package registry (OSV) |
| alpine:redis | 7.2.11-r0 · Alpine:v3.21 | Package registry (OSV) |
| alpine:valkey | 7.2.11-r0 · Alpine:v3.20 | Package registry (OSV) |
| debian:redict | 7.3.6+ds-1 · Debian:14 | Package registry (OSV) |
| debian:redis | 5:7.0.15-1~deb12u6 · Debian:12 | Package registry (OSV) |
| debian:valkey | 8.1.1+dfsg1-3+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:redis | 7.2.4-150600.3.18.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:redis7 | 7.0.8-150600.8.19.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:valkey | 8.0.6-150600.13.17.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:redis | 0:6.2.20-1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-debuginfo | 0:6.2.20-1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-debugsource | 0:6.2.20-1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-devel | 0:6.2.20-1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:redis-doc | 0:6.2.20-1.el9_6 · Red Hat:enterprise_linux:9::appstream | Package registry (OSV) |
| red hat:valkey | 0:8.0.6-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:valkey-debuginfo | 0:8.0.6-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:valkey-debugsource | 0:8.0.6-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:valkey-devel | 0:8.0.6-1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| rocky linux:redis | 0:6.2.20-1.el9_6 · Rocky Linux:9 | Package registry (OSV) |
| rocky linux:valkey | 0:8.0.6-1.el10_0 · Rocky Linux:10 | Package registry (OSV) |
| suse:redis | 7.2.4-150600.3.18.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:redis7 | 7.0.8-150600.8.19.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:valkey | 8.0.6-150600.13.17.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Nuclei detection template ×1
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Nuclei detection template | Nuclei template CVE-2025-46819 | — |
| Proof-of-concept repository on GitHub | stars:5 | 2025-10-07 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+3 d
- TodayNov 10, 2026+403 d
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-468170 days apartLua library commands may lead to integer overflow and potential RCE36Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.