CVE-2026-42570

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 69% 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
Trending — Patch released this week
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

A fix is available — apply it.

Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From version 5.6.3 to before version 5.8.1, devalue.parse could, due to quirks in some JavaScript engines, be convinced to allocate much more memory than was needed when deserializing sparse arrays, leading to excessive memory consumption. This issue has been patched in version 5.8.1.

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

Published

June 9, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jun 9, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

DoS via sparse array deserialization · Advisory · sveltejs/devalue · GitHub

https://github.com/sveltejs/devalue/security/advisories/GHSA-77vg-94rm-hx3p
github_release Patch Available

v5.8.1

Patch available: sveltejs/devalue v5.8.1

https://github.com/sveltejs/devalue/releases/tag/v5.8.1
github_commit Patch Available

commit 206ca6712fbc (sveltejs/devalue)

Patch available: sveltejs/devalue v5.8.1 (contains commit 206ca6712fbc)

https://github.com/sveltejs/devalue/commit/206ca6712fbc380a4571c59de9ab04b91110792d

Vendor Advisories for CVE-2026-42570(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhtas/rekor-search-ui-rhel9:17833271852026-07-09redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
devalue—5.8.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 93× 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 103 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42570?
CVE-2026-42570 is a high vulnerability published on June 9, 2026. Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From version 5.6.3 to before version 5.8.1, devalue.parse could, due to quirks in some JavaScript engines, be convinced to allocate much more memory than was needed when…
When was CVE-2026-42570 disclosed?
CVE-2026-42570 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42570 actively exploited?
CVE-2026-42570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42570?
CVE-2026-42570 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42570?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42570, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42570

Explore →

Is Your Infrastructure Affected by CVE-2026-42570?

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

Start Free Scan →Browse All CVEs