# CVE-2026-42570: Svelte devalue denial of service in devalue.parse

Source: https://junglewise.ai/threats/cve-2026-42570-svelte-devalue-denial-of-service-in-devalue-parse  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-09. Updated: 2026-06-09  
License: CC BY 4.0 with a link back

CVE-2026-42570 · Severity: high · CVSS 7.5 · Published 2026-06-09

A vulnerability in the Svelte 'devalue' library, which is used to serialize and deserialize JavaScript data, can be exploited to cause a denial-of-service (DoS) condition. By providing specially crafted data, an attacker can force the application to consume excessive amounts of memory, potentially crashing the service or making it unresponsive. This affects applications that use devalue to process untrusted user input.

Technologies: [devalue (npm)](https://junglewise.ai/threats/technologies/devalue). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-42570 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-42570 being exploited in the wild.

**How severe is CVE-2026-42570?** High severity, with a CVSS score of 7.5, published 9 June 2026.

**Which products and versions are affected?** devalue (npm) >= 5.6.3, <= 5.8.0, SEMVER:introduced=5.6.3,fixed=5.8.1.

**Is there a fix for CVE-2026-42570?** Yes. devalue (npm): upgrade to 5.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-42570 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-42570?** Check whether you run devalue (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- devalue (npm): upgrade to 5.8.1 or later

  ```sh
  npm install devalue@5.8.1
  ```


## Technical details

The 'devalue.parse' function in Svelte's devalue library is vulnerable to a resource exhaustion issue (CWE-770). Due to specific behaviors in certain JavaScript engines, the deserialization of sparse arrays can be manipulated to allocate significantly more memory than required. An unauthenticated remote attacker can exploit this by sending a malicious payload containing a sparse array, leading to a Denial of Service (DoS) through memory exhaustion. The issue is fixed in version 5.8.1.

## Affected products

- Svelte devalue >= 5.6.3, <= 5.8.0

## Identifiers

- CVE-2026-42570
- GHSA-77vg-94rm-hx3p

## Timeline

- 2026-05-14: disclosed
- 2026-05-14: advisory
- 2026-05-14: patched

## References

- [https://api.github.com/users/elliott-with-the-longest-name-on-github](https://api.github.com/users/elliott-with-the-longest-name-on-github)
- [https://github.com/elliott-with-the-longest-name-on-github](https://github.com/elliott-with-the-longest-name-on-github)
- [https://api.github.com/users/elliott-with-the-longest-name-on-github/gists%7B/gist_id%7D](https://api.github.com/users/elliott-with-the-longest-name-on-github/gists%7B/gist_id%7D)
- [https://api.github.com/users/elliott-with-the-longest-name-on-github/repos](https://api.github.com/users/elliott-with-the-longest-name-on-github/repos)
- [https://avatars.githubusercontent.com/u/76245373?v=4](https://avatars.githubusercontent.com/u/76245373?v=4)
- [https://api.github.com/users/elliott-with-the-longest-name-on-github/events%7B/privacy%7D](https://api.github.com/users/elliott-with-the-longest-name-on-github/events%7B/privacy%7D)

## Related threats

- [devalue uneval sparse-array CPU amplification](https://junglewise.ai/threats/devalue-residual-sparse-array-cpu-amplification-in-uneval-288a909c)
- [devalue quadratic expansion in uneval with repeated primitives](https://junglewise.ai/threats/devalue-repeated-primitive-strings-cause-quadratic-expansion-in-uneval-9363872e)
- [devalue sparse arrays excessive memory allocation in uneval](https://junglewise.ai/threats/devalue-sparse-arrays-emitted-by-uneval-cause-eager-allocation-when-79528840)
- [devalue ArrayBuffer allocation bypass via custom reviver](https://junglewise.ai/threats/devalue-custom-arraybuffer-revivers-can-bypass-typed-array-allocation-ecd9322f)
- [devalue stringifyAsync unhandled promise rejection](https://junglewise.ai/threats/devalue-stringifyasync-can-cause-an-unhandled-rejection-despite-a-1b814ff8)