devalue vulnerable to denial of service due to memory exhaustion in devalue.parse
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.6%
exploitation probability
0.6%top 56% of all CVEs
observed exploitation
nono source reports it
Svelte devalue is a JavaScript library that serializes values into strings when JSON.stringify isn't sufficient for the job. From 5.3.0 to 5.6.1, certain inputs can cause devalue.parse to consume excessive CPU time and/or memory, potentially leading to denial of service in systems that parse input from untrusted sources. This affects applications using devalue.parse on externally-supplied data. The root cause is the typed array hydration expecting an ArrayBuffer as input, but not checking the assumption before creating the typed array. This vulnerability is fixed in 5.6.2.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Affected products
sveltejs · devalueReferences
https://access.redhat.com/errata/RHSA-2026:2144https://access.redhat.com/errata/RHSA-2026:2926https://access.redhat.com/security/cve/CVE-2026-22774https://bugzilla.redhat.com/show_bug.cgi?id=2430095https://github.com/sveltejs/devalue/commit/e46afa64dd2b25aa35fb905ba5d20cea63aabbf7https://github.com/sveltejs/devalue/releases/tag/v5.6.2https://github.com/sveltejs/devalue/security/advisories/GHSA-vw5p-8cq8-m7mvhttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-22774.json