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 manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. 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 restrict EVAL and EVALSHA commands.
CVE-2025-49844
CRITICALNVD 9.99.9Trending — 3 sources updated this weekWeaponizedEG-KEV Tier 2: WeaponizedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 2 is not evidence of exploitation. It means a Metasploit module exists, or Exploit-DB marks a public exploit verified, or CISA's SSVC data says "public PoC" and EPSS is 50% or more. EchelonGraph does not test whether exploit code works.Signals for this CVE: CISA's SSVC exploitation value: public PoC, EPSS in the top 5%, EPSS 50% or more, other public exploit code (a GitHub or vendor proof of concept, or an Exploit-DB entry not marked verified).First public exploit code on record: 2019-04-13 (GitHub PoC ksnnd32/redis_exploit)EchelonGraph confidence 70%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 83% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Also known asEUVD-2025-33178 (ENISA EUVD)Source: ENISA EUVD
9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- High exploitation likelihood — EPSS 83%
- Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 83%CVSS: 9.9Exploit: Public PoCExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 9.9CRITICALmedium confidence
- EG Risk
- 78EG Risk 78/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity99% × 45%Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation83% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 83%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 83% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 3, 2025
Last Modified
October 19, 2026
Advisory Details (5)
Auto-updated Oct 26, 2026Patch available. Sources: github_commit, github_release, github.
Web page
GitHub - lastvocher/redis-CVE-2025-49844 · GitHub
https://github.com/lastvocher/redis-CVE-2025-49844Web page
oss-security - redis: CVE-2025-49844: Lua Use-After-Free may lead to remote code execution
http://www.openwall.com/lists/oss-security/2025/10/07/2GitHub advisoryMentions a patch (unverified)
Lua Use-After-Free may lead to remote code execution · Advisory · redis/redis · GitHub
https://github.com/redis/redis/security/advisories/GHSA-4789-qfc9-5f9qGitHub release Patch Available
8.2.2
Patch available: redis/redis 8.2.2
https://github.com/redis/redis/releases/tag/8.2.2GitHub commit Patch Available
commit d5728cb5795c (redis/redis)
Patch available: redis/redis 8.2.8 (contains commit d5728cb5795c)
https://github.com/redis/redis/commit/d5728cb5795c966c5b5b1e0f0ac576a7e69af539Vendor Advisories for CVE-2025-49844(19)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- RHSA-2025:23207Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift GitOps v1.16.5 security update
- RHSA-2025:23206Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift GitOps v1.17.3 security update
- RHSA-2025:23203Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat OpenShift GitOps v1.18.2 security update
- RHSA-2025:21936Red Hat Product SecurityHigh
Red Hat Security Advisory: valkey security update
- RHSA-2025:21916Red Hat Product SecurityHigh
Red Hat Security Advisory: valkey security update
- RHSA-2025:20955Red Hat Product SecurityHigh
Red Hat Security Advisory: redis:7 security update
- RHSA-2025:20926Red Hat Product SecurityHigh
Red Hat Security Advisory: redis security update
- RHSA-2025:19675Red Hat Product SecurityHigh
Red Hat Security Advisory: valkey security update
- +11 more
Patch Availability(24)
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(12 across 9 ecosystems)
Debian:14(3)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| redict | 7.3.0+ds-1 ... 7.3.6+ds-1~bpo13+1 (11 versions) |
| — |
| redis | 5:8.0.2-3 |
| — |
| valkey | 8.1.1+dfsg1-3 |
| — |
Debian:13(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| redis | 5:8.0.2-3 |
| — |
| valkey | 8.1.1+dfsg1-3 |
| — |
Alpine:v3.20(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| valkey | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| valkey | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| valkey | — |
| — |
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| valkey | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| valkey | — |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| redis | 5:6.0.15-1 ... 5:6.0.16-1~bpo11+1 (11 versions) |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| redis | 5:7.0.11-1 ... 5:7.0.15-1~deb12u5 (13 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(6)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 18× in last 7d / 66× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 97 of 155 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 58 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-02 13:09 UTCEG score recompute
- 2026-11-02 13:09 UTCVendor advisory
- 2026-11-01 15:20 UTCVendor advisory
- 2026-10-31 17:34 UTCEG score recompute
- 2026-10-31 17:34 UTCVendor advisory
- 2026-10-30 19:49 UTCEG score recompute
- 2026-10-30 19:49 UTCVendor advisory
- 2026-10-30 16:32 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-29 22:01 UTCEG score recompute
- 2026-10-29 22:01 UTCVendor advisory
- 2026-10-29 16:31 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-29 00:15 UTCEG score recompute
- 2026-10-29 00:15 UTCVendor advisory
- 2026-10-28 02:31 UTCEG score recompute
- 2026-10-28 02:31 UTCVendor advisory
- 2026-10-27 16:30 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-27 04:40 UTCEG score recompute
- 2026-10-27 04:40 UTCVendor advisory
- 2026-10-26 02:26 UTCEG score recompute
- 2026-10-26 02:26 UTCVendor advisory
- 2026-10-25 16:31 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-25 16:21 UTCEG score recompute
- 2026-10-25 04:40 UTCEG score recompute
- 2026-10-25 04:40 UTCVendor advisory
- 2026-10-24 16:31 UTCEPSS rescoreEPSS 83% · 99th percentile
Show 72 moreShow fewer
- 2026-10-24 06:55 UTCEG score recompute
- 2026-10-24 06:55 UTCVendor advisory
- 2026-10-23 16:30 UTCEPSS rescoreEPSS 83% · 99th percentile
- 2026-10-23 09:09 UTCEG score recompute
- 2026-10-23 09:09 UTCVendor advisory
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-22 11:16 UTCEG score recompute
- 2026-10-22 11:16 UTCVendor advisory
- 2026-10-21 16:31 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-21 13:31 UTCEG score recompute
- 2026-10-21 13:31 UTCVendor advisory
- 2026-10-20 15:35 UTCEG score recompute
- 2026-10-20 15:35 UTCVendor advisory
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-19 16:28 UTCVendor advisory
- 2026-10-19 08:42 UTCEG score recompute
- 2026-10-19 08:42 UTCVendor advisory
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-18 10:40 UTCVendor advisory
- 2026-10-18 05:29 UTCEG score recompute
- 2026-10-17 12:40 UTCEG score recompute
- 2026-10-17 12:40 UTCVendor advisory
- 2026-10-16 16:38 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-16 14:53 UTCEG score recompute
- 2026-10-16 14:53 UTCVendor advisory
- 2026-10-15 16:16 UTCEG score recompute
- 2026-10-15 16:16 UTCVendor advisory
- 2026-10-14 16:31 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-14 10:21 UTCEG score recompute
- 2026-10-14 10:21 UTCVendor advisory
- 2026-10-13 16:32 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-13 08:49 UTCVendor advisory
- 2026-10-12 16:59 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-12 11:01 UTCVendor advisory
- 2026-10-11 20:33 UTCEG score recompute
- 2026-10-11 18:45 UTCEG score recompute
- 2026-10-11 15:20 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-05 17:42 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-10-02 03:11 UTCOSV refresh
- 2026-09-30 15:02 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-28 13:50 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-26 15:58 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-26 00:25 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-24 14:02 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-23 13:47 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-21 21:06 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-18 19:27 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-16 14:07 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-12 21:06 UTCOSV refresh
- 2026-09-11 14:52 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-10 09:34 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-08 21:59 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-06 13:46 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-05 15:28 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-04 05:06 UTCEPSS rescoreEPSS 82% · 99th percentile
- 2026-09-02 14:11 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-30 19:16 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-28 21:40 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-26 14:45 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-25 13:48 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-25 01:56 UTCOSV refresh
- 2026-08-24 14:16 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-24 09:22 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-21 23:48 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-19 17:03 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-15 01:29 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-11 13:41 UTCEPSS rescoreEPSS 87% · 99th percentile
- 2026-08-08 19:25 UTCOSV refresh
- 2026-08-04 10:37 UTCEPSS rescoreEPSS 87% · 99th percentile
Publicly available exploits
(9 references)Public exploit code is referenced for this CVE (8 GitHub PoCs), as is 1 Nuclei detection template. A detection template checks whether a system is affected; it is not necessarily exploit code. Defenders should treat patch urgency accordingly.
- GitHub PoCsaneki/cve-2025-49844Published Oct 31, 2025
Proof-of-concept for CVE-2025-49844
Open source ↗ - Nucleijavascript/cves/2025/CVE-2025-49844.yamlPublished Oct 11, 2025
Redis Lua Parser < 8.2.2 - Use After Free
Open source ↗ - GitHub PoCMiclelsonCN/CVE-2025-49844_POCPublished Oct 9, 2025
CVE-2025-49844 POC
Open source ↗ - Open source ↗GitHub PoCpedrorichil/CVE-2025-49844Published Oct 8, 2025
- GitHub PoCdwisiswant0/CVE-2025-49844Published Oct 7, 2025
CVE-2025-49844 – Redis Lua Parser Use-After-Free
Open source ↗ - Open source ↗GitHub PoClastvocher/redis-CVE-2025-49844Published Oct 7, 2025
- GitHub PoCraminfp/redis_exploitPublished Oct 7, 2025
CVE-2025-49844 (RediShell)
Open source ↗ - GitHub PoCZain3311/CVE-2025-49844Published Apr 6, 2022
🚨 Exploit the CVE-2025-49844 Redis Lua interpreter UAF vulnerability to execute arbitrary shellcode and gain persistent backdoor access.
Open source ↗ - GitHub PoCksnnd32/redis_exploitPublished Apr 13, 2019
🔍 Explore and test the CVE-2025-49844 (RediShell) vulnerability in Redis with this practical lab environment for secure education and research.
Open source ↗
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.20:valkey
Same vendor
9 shownredhat:RHSA-2025:18931 · redhat:RHSA-2025:19237 · redhat:RHSA-2025:23203
Frequently asked(5)
What is CVE-2025-49844?
CVE-2025-49844 is a critical-severity vulnerability; its CVE record was published on October 3, 2025. 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 manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all…
When was the CVE record for CVE-2025-49844 published?
The CVE record for CVE-2025-49844 was published on October 3, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-49844 actively exploited?
CVE-2025-49844 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-49844?
CVE-2025-49844 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-49844?
A fix for CVE-2025-49844 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-49844 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-49844
Is Your Infrastructure Affected by CVE-2025-49844?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.