Sveltejs devalue before 5.9.3 Memory Exhaustion via uneval Sparse Arrays
cve-program · CVE-2026-123564
PublishedSveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array serialized by an application can exhaust memory in the browser or runtime evaluating the output.
Read the publisher's advisoryeuvd · EUVD-2026-119449
PublishedSveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array serialized by an application can exhaust memory in the browser or runtime evaluating the output.
Read the publisher's advisorynvd · CVE-2026-123564
PublishedSveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very large sparse array serialized by an application can exhaust memory in the browser or runtime evaluating the output.
Read the publisher's advisoryosv · GHSA-wf3x-273g-mvxv
PublishedEvaluating legitimate `uneval` output for a sparse array can allocate memory proportional to its declared length. A tiny serialized value can therefore cause large memory allocation in a consuming browser/runtime. This occurs during evaluation of generated code, not in default `parse` sparse-array construction. You would only be affected by this if you were serializing very large sparse arrays and then evaluating the results. In the general use case for `uneval` of sending data to the client, the worst that could happen is the browser tab running out of memory.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-123564 · CVE overview and exploitation status
cve-program · CVE-2026-123564
- https://github.com/sveltejs/devalue/security/advisories/GHSA-wf3x-273g-mvxv
- https://www.vulncheck.com/advisories/sveltejs-devalue-before-5.9.3-memory-exhaustion-via-uneval-sparse-arrays
euvd · EUVD-2026-119449
- https://github.com/sveltejs/devalue/security/advisories/GHSA-wf3x-273g-mvxv
- https://www.vulncheck.com/advisories/sveltejs-devalue-before-5.9.3-memory-exhaustion-via-uneval-sparse-arrays
nvd · CVE-2026-123564
- https://github.com/sveltejs/devalue/security/advisories/GHSA-wf3x-273g-mvxv
- https://www.vulncheck.com/advisories/sveltejs-devalue-before-5.9.3-memory-exhaustion-via-uneval-sparse-arrays
osv · GHSA-wf3x-273g-mvxv
Related changes
Linked by CVE identifier- Sveltejs devalue from 1.0.0 before 5.9.3 contains a memory exhaustion flaw in uneval, whose generated code for sparse arrays allocates memory proportional to the array's declared length when evaluated. Attackers who can influence a very lar… · Advisory content revised · 14 Nov 2026
- Sveltejs devalue before 5.9.3 Memory Exhaustion via uneval Sparse Arrays · Newly collected advisory · 8 Nov 2026
- devalue: Sparse arrays emitted by uneval cause eager allocation when evaluated · Advisory content revised · 8 Nov 2026