CVE-2024-46981: Redis' Lua library commands may lead to remote code execution
Noroxi assessment
Priority: Plan (action score 41/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.1% (FIRST EPSS); higher than 94.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: redis redis 7.4.2; azl3 valkey 8.0.1-1 on Azure Linux 3.0 8.0.2-1; azl3 valkey 8.0.2-1 on Azure Linux 3.0 8.0.2-1.
- Severity is disputed: the assigning authority (CNA) scores it 7.0, NVD 9.8.
Add it to your regular patch cycle. Upgrade to redis redis 7.4.2; azl3 valkey 8.0.1-1 on Azure Linux 3.0 8.0.2-1; azl3 valkey 8.0.2-1 on Azure Linux 3.0 8.0.2-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. An authenticated user may use a specially crafted Lua script to manipulate the garbage collector and potentially lead to remote code execution. The problem is fixed in 7.4.2, 7.2.7, and 6.2.17. An additional workaround to mitigate the problem without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.
- BDU:2025-00214
- ALSA-2025:0595
- ALSA-2025:0692
- ALSA-2025:0693
- DLA-4025-1
- DSA-5856-1
- openSUSE-SU-2025:14638-1
- openSUSE-SU-2025:15293-1
- RHSA-2025:0398
- RHSA-2025:0399
- RHSA-2025:0400
- RHSA-2025:0566
- RHSA-2025:0595
- RHSA-2025:0640
- RHSA-2025:0685
- RHSA-2025:0689
- RHSA-2025:0692
- RHSA-2025:0693
- RLSA-2025:0595
- RLSA-2025:0692
- Published
- Jan 6, 2025
- Updated
- Jun 17, 2026
- EPSS
- 8.1% · 94th percentile
- CWE
- CWE-416
Report tools
Action score
41
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 8.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.8
- CNA · GitHub_M
- 7.0
- 2.8 point gap
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/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.
Is Redis on your server exposed to the internet?Run a port scan
Is your version affected? Check itNoroxi 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.
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 scanVersions 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
- >= 7.4.0, < 7.4.2, >= 7.2.0, < 7.2.7, < 6.2.17affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redis redis6.2.0 and later · before 6.2.17
- redis redis7.2.0 and later · before 7.2.7
- redis redis7.4.0 and later · before 7.4.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | redis | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:8 | redis-devel | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:8 | redis-doc | before 6.2.17-1.module_el8.10.0+3946+3de613d5 | 6.2.17-1.module_el8.10.0+3946+3de613d5 |
| AlmaLinux:9 | redis | before 6.2.17-1.el9_5 | 6.2.17-1.el9_5 |
| AlmaLinux:9 | redis | before 7.2.7-1.module_el9.5.0+134+2e645600 | 7.2.7-1.module_el9.5.0+134+2e645600 |
| AlmaLinux:9 | redis-devel | before 6.2.17-1.el9_5 | 6.2.17-1.el9_5 |
| AlmaLinux:9 | redis-devel | before 7.2.7-1.module_el9.5.0+134+2e645600 | 7.2.7-1.module_el9.5.0+134+2e645600 |
| AlmaLinux:9 | redis-doc | before 7.2.7-1.module_el9.5.0+134+2e645600 | 7.2.7-1.module_el9.5.0+134+2e645600 |
| AlmaLinux:9 | redis-doc | before 6.2.17-1.el9_5 | 6.2.17-1.el9_5 |
| Alpine:v3.15 | redis | from 6.2.0 · before 6.2.18-r0 | 6.2.18-r0 |
| Alpine:v3.18 | redis | from 6.2.0 · before 7.0.15-r2 | 7.0.15-r2 |
| Alpine:v3.19 | redis | from 6.2.0 · before 7.2.7-r0 | 7.2.7-r0 |
| Alpine:v3.20 | redict | before 7.3.2-r0 | 7.3.2-r0 |
| Alpine:v3.20 | valkey | before 7.2.8-r0 | 7.2.8-r0 |
| Debian:11 | redis | before 5:6.0.16-1+deb11u5 | 5:6.0.16-1+deb11u5 |
| Debian:12 | redis | before 5:7.0.15-1~deb12u3 | 5:7.0.15-1~deb12u3 |
| Debian:13 | redis | before 5:7.0.15-3 | 5:7.0.15-3 |
| Debian:13 | valkey | before 8.0.2+dfsg1-1 | 8.0.2+dfsg1-1 |
| openSUSE:Leap 15.6 | redis | before 7.2.4-150600.3.6.1 | 7.2.4-150600.3.6.1 |
| openSUSE:Leap 15.6 | redis7 | before 7.0.8-150600.8.6.1 | 7.0.8-150600.8.6.1 |
| openSUSE:Tumbleweed | redis | before 8.0.2-1.1 | 8.0.2-1.1 |
| openSUSE:Tumbleweed | valkey | before 8.0.2-1.1 | 8.0.2-1.1 |
| Red Hat:enterprise_linux:8::appstream | redis | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
| Red Hat:enterprise_linux:8::appstream | redis-debuginfo | before 0:6.2.17-1.module+el8.10.0+22680+748527fd | 0:6.2.17-1.module+el8.10.0+22680+748527fd |
+56
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…KEV100Now
- 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-2024-31228Oct 7, 2024 · Denial-of-service due to unbounded pattern matching in Redis26Monitor
- ← EarlierCVE-2024-31449Oct 7, 2024 · Lua library commands may lead to stack overflow and RCE in Redis36Monitor
- Later →CVE-2024-51741Jan 6, 2025 · Redis allows denial-of-service due to malformed ACL selectors17Monitor
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 | 7.4.2 · description | Vendor (CNA) |
| azl3 valkey 8.0.1-1 on Azure Linux 3.0 | 8.0.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 valkey 8.0.2-1 on Azure Linux 3.0 | 8.0.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 redis 6.2.16-1 on CBL Mariner 2.0 | 6.2.17-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 redis 6.2.16-1 on CBL-Mariner 2.0 | 6.2.17-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 redis 6.2.17-1 on CBL Mariner 2.0 | 6.2.17-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:redis | 6.2.17-1.module_el8.10.0+3946+3de613d5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:redis-devel | 6.2.17-1.module_el8.10.0+3946+3de613d5 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:redis-doc | 6.2.17-1.module_el8.10.0+3946+3de613d5 · AlmaLinux:8 | Package registry (OSV) |
| alpine:redict | 7.3.2-r0 · Alpine:v3.20 | Package registry (OSV) |
| alpine:redis | 6.2.18-r0 · Alpine:v3.15 | Package registry (OSV) |
| alpine:valkey | 7.2.8-r0 · Alpine:v3.20 | Package registry (OSV) |
| debian:redict | 7.3.2+ds-1 · Debian:14 | Package registry (OSV) |
| debian:redis | 5:7.0.15-1~deb12u3 · Debian:12 | Package registry (OSV) |
| debian:valkey | 8.0.2+dfsg1-1 · Debian:13 | Package registry (OSV) |
| opensuse:redis | 7.2.4-150600.3.6.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:redis7 | 7.0.8-150600.8.6.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:valkey | 8.0.2-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:redis | 0:6.2.7-1.el9_2.1 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:redis-debuginfo | 0:6.2.7-1.el9_2.1 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:redis-debugsource | 0:6.2.7-1.el9_2.1 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:redis-devel | 0:6.2.7-1.el9_2.1 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| red hat:redis-doc | 0:6.2.7-1.el9_2.1 · Red Hat:rhel_eus:9.2::appstream | Package registry (OSV) |
| rocky linux:redis | 0:6.2.17-1.module+el8.10.0+1923+5b85c6a7 · Rocky Linux:8 | Package registry (OSV) |
| suse:redis | 6.0.14-150200.6.32.1 · SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | Package registry (OSV) |
| suse:redis | 7.2.4-150600.3.6.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP6 | Package registry (OSV) |
| suse:redis7 | 7.0.8-150500.3.15.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:redis7 | 7.0.8-150600.8.6.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
- Proof-of-concept repository on GitHub ×2
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 |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:5 | 2025-03-19 |
| Proof-of-concept repository on GitHub | stars:0 | 2025-03-21 |
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+71 d
- TodayNov 14, 2026+676 d
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-49844270 days apartRedis Lua Use-After-Free may lead to remote code execution64This week
- CVE-2026-23479484 days apartredis-server use-after-free in unblock client flow may allow remote code execution31Monitor
- CVE-2026-23631484 days apartredis-server Lua use-after-free may allow remote code execution25Monitor
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- 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.