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 67% 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.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 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)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

June 9, 2026

Last Modified

August 24, 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(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrh-podman-desktop-0:1.1.2-1.el10_22026-08-20redhat
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 26× in last 7d / 106× 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 176 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 August 24, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 67.4% of all scored CVEs.
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