Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
7.5

CVE-2026-42570: Svelte Excessive Memory Consumption via Sparse Array Deserialization

CVE-2026-42570 · published 4 months ago
Summary

A bug in Svelte's `devalue.parse` function can cause it to use too much memory when handling certain types of data. This can lead to performance issues or even crashes. To fix this, update to the latest version of Svelte.

What to do
  • Update GitHub Actions devalue to version 5.8.1.
  • Update svelte devalue to version 5.8.1 or later.
Affected software
Ecosystem VendorProductAffected versions
npm GitHub Actions devalue >= 5.6.3, <= 5.8.0
Fix: upgrade to 5.8.1
– svelte devalue >= 5.6.3, < 5.8.1
cpe:2.3:a:svelte:devalue:*:*:*:*:*:node.js:*:*
Original advisory text
Svelte devalue: DoS via sparse array deserialization
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.
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker partial control
Severity
7.5 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-770Allocation of Resources Without Limits
Timeline
Published9 Jun 2026
Updated4 Nov 2026
First seen14 May 2026
Sources
Track software like this
Free during beta