CVE-2026-54341

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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, secondary
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

Dragonfly is an in-memory data store built for modern application workloads. Prior to 1.39.0, a crafted RESTORE payload triggers an out-of-bounds read in DragonflyDB's listpack collection loaders, crashing the entire server process (SIGSEGV). Because DragonflyDB requires no authentication by default and RESTORE is a normal keyspace command, an unauthenticated remote attacker can crash the server with a single ~24-byte command — a remote, repeatable denial of service. This vulnerability is fixed in 1.39.0.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
32.2%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (2)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_pr, github.
github Patch Available🟡 PoC Available

RESTORE operations may crash the server · Advisory · dragonflydb/dragonfly · GitHub

https://github.com/dragonflydb/dragonfly/security/advisories/GHSA-cwjr-j869-h8q9
github_pr

fix: deep-validate listpack/intset payloads on RESTORE

Fix merged in dragonflydb/dragonfly PR #7502 on 2026-06-03 — awaiting tagged release

https://github.com/dragonflydb/dragonfly/pull/7502

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 75× 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-15 23:35 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 12:39 UTCEG score recompute
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-15 01:40 UTCEG score recompute
  8. 2026-07-14 14:44 UTCEG score recompute
  9. 2026-07-14 03:48 UTCEG score recompute
  10. 2026-07-13 22:31 UTCEPSS rescore
  11. 2026-07-13 16:52 UTCEG score recompute
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 05:56 UTCEG score recompute
  15. 2026-07-12 19:00 UTCEG score recompute
  16. 2026-07-12 08:03 UTCEG score recompute
  17. 2026-07-12 05:46 UTCEPSS rescore
  18. 2026-07-11 21:07 UTCEG score recompute
  19. 2026-07-11 10:11 UTCEG score recompute
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-10 23:14 UTCEG score recompute
  23. 2026-07-10 12:17 UTCEG score recompute
  24. 2026-07-10 01:19 UTCEG score recompute
  25. 2026-07-09 19:10 UTCEPSS rescore
Show 50 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 14:22 UTCEG score recompute
  3. 2026-07-09 03:23 UTCEG score recompute
  4. 2026-07-08 16:23 UTCEG score recompute
  5. 2026-07-08 15:16 UTCEPSS rescore
  6. 2026-07-08 15:16 UTCEPSS rescore
  7. 2026-07-08 05:26 UTCEG score recompute
  8. 2026-07-07 18:24 UTCEG score recompute
  9. 2026-07-07 13:46 UTCEPSS rescore
  10. 2026-07-07 13:46 UTCEPSS rescore
  11. 2026-07-07 07:28 UTCEG score recompute
  12. 2026-07-06 20:28 UTCEG score recompute
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 16:27 UTCEPSS rescore
  15. 2026-07-06 09:31 UTCEG score recompute
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 22:35 UTCEG score recompute
  19. 2026-07-05 11:39 UTCEG score recompute
  20. 2026-07-05 02:31 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-05 00:43 UTCEG score recompute
  23. 2026-07-04 13:46 UTCEG score recompute
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
  26. 2026-07-04 02:50 UTCEG score recompute
  27. 2026-07-03 15:51 UTCEG score recompute
  28. 2026-07-03 04:54 UTCEG score recompute
  29. 2026-07-02 17:59 UTCEG score recompute
  30. 2026-07-02 07:03 UTCEG score recompute
  31. 2026-07-01 20:05 UTCEG score recompute
  32. 2026-07-01 15:07 UTCEPSS rescore
  33. 2026-07-01 09:09 UTCEG score recompute
  34. 2026-06-30 23:22 UTCEPSS rescore
  35. 2026-06-30 22:13 UTCEG score recompute
  36. 2026-06-30 11:17 UTCEG score recompute
  37. 2026-06-30 00:17 UTCEG score recompute
  38. 2026-06-29 14:06 UTCEPSS rescore
  39. 2026-06-29 14:06 UTCEPSS rescore
  40. 2026-06-29 13:21 UTCEG score recompute
  41. 2026-06-29 02:25 UTCEG score recompute
  42. 2026-06-28 15:29 UTCEG score recompute
  43. 2026-06-28 14:07 UTCEPSS rescore
  44. 2026-06-28 04:56 UTCEPSS rescore
  45. 2026-06-28 04:56 UTCEPSS rescore
  46. 2026-06-28 04:33 UTCEG score recompute
  47. 2026-06-27 17:36 UTCEG score recompute
  48. 2026-06-27 06:39 UTCEG score recompute
  49. 2026-06-26 19:42 UTCEG score recompute
  50. 2026-06-26 19:41 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54341?
CVE-2026-54341 is a high vulnerability published on June 26, 2026. Dragonfly is an in-memory data store built for modern application workloads. Prior to 1.39.0, a crafted RESTORE payload triggers an out-of-bounds read in DragonflyDB's listpack collection loaders, crashing the entire server process (SIGSEGV). Because DragonflyDB requires no authentication by…
When was CVE-2026-54341 disclosed?
CVE-2026-54341 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54341 actively exploited?
CVE-2026-54341 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54341?
CVE-2026-54341 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-54341?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54341, 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-54341

Explore →

Is Your Infrastructure Affected by CVE-2026-54341?

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

Start Free Scan →Browse All CVEs