CVE-2023-36824

HIGHNVD 7.48.8▲
EchelonGraph scoreHIGH confidence

Score elevated to 8.8 because EPSS predicts 77% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 7.4 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 77%
CISA-KEV: Not listedEPSS PROB: 77%CVSS: 7.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Redis is an in-memory database that persists on disk. In Redit 7.0 prior to 7.0.12, extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption and potentially remote code execution. Several scenarios that may lead to authenticated users executing a specially crafted COMMAND GETKEYS or COMMAND GETKEYSANDFLAGSand authenticated users who were set with ACL rules that match key names, executing a specially crafted command that refers to a variadic list of key names. The vulnerability is patched in Redis 7.0.12.

CVSS v3
7.4
EG Score
8.8(high)
EG Risk
71(Track)
EG Risk 71/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation77% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
77%
EPSS %ILE
100%
KEV
Not listed

Published

July 11, 2023

Last Modified

April 10, 2025

References (10)

Weakness Classification(3)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-26 14:52 UTCEPSS rescore
  2. 2026-07-24 14:16 UTCEPSS rescore
  3. 2026-07-23 02:24 UTCEG score recompute▲ 1.40
  4. 2026-07-22 23:11 UTCEG score recompute▼ 1.60
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-21 15:23 UTCEPSS rescore
  7. 2026-07-21 15:23 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-15 16:56 UTCEPSS rescore
  10. 2026-07-15 15:49 UTCOSV refresh
  11. 2026-07-12 05:45 UTCEPSS rescore
  12. 2026-07-09 19:08 UTCEPSS rescore
  13. 2026-07-09 19:08 UTCEPSS rescore
  14. 2026-07-08 15:13 UTCEPSS rescore
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-06 16:26 UTCEPSS rescore
  17. 2026-07-02 16:59 UTCEPSS rescore
  18. 2026-07-01 15:04 UTCEPSS rescore
  19. 2026-06-30 23:21 UTCEPSS rescore
  20. 2026-06-30 23:21 UTCEPSS rescore
  21. 2026-06-28 14:06 UTCEPSS rescore
  22. 2026-06-28 14:06 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-27 16:04 UTCOSV refresh
Show 42 more
  1. 2026-06-27 03:07 UTCEPSS rescore
  2. 2026-06-27 03:07 UTCEPSS rescore
  3. 2026-06-25 13:48 UTCEPSS rescore
  4. 2026-06-25 13:48 UTCEPSS rescore
  5. 2026-06-24 14:04 UTCEPSS rescore
  6. 2026-06-24 14:03 UTCEPSS rescore
  7. 2026-06-23 21:31 UTCEPSS rescore
  8. 2026-06-23 21:31 UTCEPSS rescore
  9. 2026-06-21 01:58 UTCEPSS rescore
  10. 2026-06-21 01:58 UTCEPSS rescore
  11. 2026-06-17 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-15 17:47 UTCEPSS rescore
  14. 2026-06-14 23:16 UTCEPSS rescore
  15. 2026-06-13 22:59 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-10 22:17 UTCEPSS rescore
  18. 2026-06-10 02:47 UTCOSV refresh
  19. 2026-06-06 13:46 UTCEPSS rescore
  20. 2026-06-06 13:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-05 06:09 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-04 13:11 UTCEPSS rescore
  27. 2026-06-01 13:51 UTCEPSS rescore
  28. 2026-06-01 13:51 UTCEPSS rescore
  29. 2026-05-31 22:30 UTCEPSS rescore
  30. 2026-05-31 22:29 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-29 13:43 UTCEPSS rescore
  33. 2026-05-29 13:43 UTCEPSS rescore
  34. 2026-05-28 13:43 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-27 13:39 UTCEPSS rescore
  37. 2026-05-26 13:43 UTCEPSS rescore
  38. 2026-05-26 13:43 UTCEPSS rescore
  39. 2026-05-26 07:18 UTCEPSS rescore
  40. 2026-05-26 07:18 UTCEPSS rescore
  41. 2026-05-26 07:18 UTCEPSS rescore
  42. 2026-05-24 21:34 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-36824?
CVE-2023-36824 is a high vulnerability published on July 11, 2023. Redis is an in-memory database that persists on disk. In Redit 7.0 prior to 7.0.12, extracting key names from a command and a list of arguments may, in some cases, trigger a heap overflow and result in reading random heap memory, heap corruption and potentially remote code execution. Several…
When was CVE-2023-36824 disclosed?
CVE-2023-36824 was first published in the National Vulnerability Database on July 11, 2023, with the most recent update on April 10, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-36824 actively exploited?
CVE-2023-36824 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 77% probability of exploitation in the next 30 days, which ranks it in the top 0.5% of all scored CVEs.
What is the CVSS score of CVE-2023-36824?
CVE-2023-36824 has a CVSS v3 base score of 7.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.8.
How do I remediate CVE-2023-36824?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-36824, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-36824

Explore →

Is Your Infrastructure Affected by CVE-2023-36824?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs