CVE-2026-25243

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 71% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 3%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
85.7%
KEV
Not listed

Published

May 5, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated May 5, 2026
Patch available. Sources: github.
github Patch Available

Invalid Memory Access in Redis RESTORE Command May Lead to Remote Code Execution · Advisory · redis/redis · GitHub

https://github.com/redis/redis/security/advisories/GHSA-c8h9-259x-jff4
generic

Release 8.6.3 · redis/redis · GitHub

https://github.com/redis/redis/releases/tag/8.6.3

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatredis:7-9080020260521083756.92026-06-11redhat
redhatvalkey-0:8.0.9-1.el10_22026-06-11redhat
redhatredis-0:6.2.22-1.el9_82026-06-04redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 79× 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.

Showing the most recent 100 of 137 total refreshes for this CVE.

  1. 2026-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-01 15:06 UTCEPSS rescore
  9. 2026-07-01 15:06 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-24 14:05 UTCEPSS rescore
  22. 2026-06-23 21:33 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 75 more
  1. 2026-06-21 14:56 UTCEPSS rescore
  2. 2026-06-21 14:56 UTCEPSS rescore
  3. 2026-06-21 01:59 UTCEPSS rescore
  4. 2026-06-21 01:59 UTCEPSS rescore
  5. 2026-06-19 19:25 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-17 17:53 UTCEPSS rescore
  9. 2026-06-17 17:53 UTCEPSS rescore
  10. 2026-06-16 17:52 UTCEPSS rescore
  11. 2026-06-15 17:48 UTCEPSS rescore
  12. 2026-06-15 06:27 UTCEG score recompute
  13. 2026-06-15 06:27 UTCVendor advisory
  14. 2026-06-14 23:18 UTCEPSS rescore
  15. 2026-06-14 19:06 UTCEG score recompute
  16. 2026-06-14 19:06 UTCVendor advisory
  17. 2026-06-14 07:51 UTCEG score recompute
  18. 2026-06-14 07:51 UTCVendor advisory
  19. 2026-06-13 23:00 UTCEPSS rescore
  20. 2026-06-13 02:03 UTCEG score recompute
  21. 2026-06-13 02:03 UTCVendor advisory
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 07:35 UTCEG score recompute
  25. 2026-06-12 07:35 UTCVendor advisory
  26. 2026-06-11 20:20 UTCEG score recompute
  27. 2026-06-11 20:20 UTCVendor advisory
  28. 2026-06-11 14:00 UTCEPSS rescore
  29. 2026-06-11 09:06 UTCEG score recompute
  30. 2026-06-11 09:06 UTCVendor advisory
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 22:18 UTCEPSS rescore
  33. 2026-06-10 21:50 UTCEG score recompute
  34. 2026-06-10 21:50 UTCVendor advisory
  35. 2026-06-10 13:22 UTCEPSS rescore
  36. 2026-06-10 10:36 UTCEG score recompute
  37. 2026-06-10 10:36 UTCVendor advisory
  38. 2026-06-09 23:09 UTCEG score recompute
  39. 2026-06-09 23:09 UTCVendor advisory
  40. 2026-06-09 09:39 UTCEG score recompute
  41. 2026-06-09 09:39 UTCVendor advisory
  42. 2026-06-08 22:21 UTCEG score recompute
  43. 2026-06-08 22:21 UTCVendor advisory
  44. 2026-06-08 14:17 UTCEPSS rescore
  45. 2026-06-08 14:17 UTCEPSS rescore
  46. 2026-06-08 10:53 UTCEG score recompute
  47. 2026-06-08 10:53 UTCVendor advisory
  48. 2026-06-07 23:38 UTCEG score recompute
  49. 2026-06-07 23:38 UTCVendor advisory
  50. 2026-06-07 15:25 UTCEPSS rescore
  51. 2026-06-07 15:25 UTCEPSS rescore
  52. 2026-06-07 15:25 UTCEPSS rescore
  53. 2026-06-07 12:22 UTCEG score recompute
  54. 2026-06-07 12:22 UTCVendor advisory
  55. 2026-06-07 01:08 UTCEG score recompute
  56. 2026-06-07 01:08 UTCVendor advisory
  57. 2026-06-06 13:53 UTCEG score recompute
  58. 2026-06-06 13:53 UTCVendor advisory
  59. 2026-06-06 13:47 UTCEPSS rescore
  60. 2026-06-06 13:47 UTCEPSS rescore
  61. 2026-06-06 02:38 UTCEG score recompute
  62. 2026-06-06 02:38 UTCVendor advisory
  63. 2026-06-05 22:47 UTCEPSS rescore
  64. 2026-06-05 22:47 UTCEPSS rescore
  65. 2026-06-05 15:16 UTCEG score recompute
  66. 2026-06-05 15:16 UTCVendor advisory
  67. 2026-06-05 06:10 UTCEPSS rescore
  68. 2026-06-05 06:10 UTCEPSS rescore
  69. 2026-06-05 04:01 UTCEG score recompute
  70. 2026-06-05 04:01 UTCVendor advisory
  71. 2026-06-04 16:37 UTCEG score recompute
  72. 2026-06-04 13:12 UTCEPSS rescore
  73. 2026-06-04 13:12 UTCEPSS rescore
  74. 2026-06-04 05:22 UTCEG score recompute
  75. 2026-06-03 18:04 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-25243?
CVE-2026-25243 is a high vulnerability published on May 5, 2026. Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may…
When was CVE-2026-25243 disclosed?
CVE-2026-25243 was first published in the National Vulnerability Database on May 5, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-25243 actively exploited?
CVE-2026-25243 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 85.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-25243?
CVE-2026-25243 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-25243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-25243, 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-2026-25243

Explore →

Is Your Infrastructure Affected by CVE-2026-25243?

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