NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

GHSA-wf3x-273g-mvxv: devalue: Sparse arrays emitted by uneval cause eager allocation when evaluated

lowCVSS 4.0 2.3

Evaluating 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.

Published Oct 1, 2026

Affected packages

devalue

Ecosystem
npm
Affected
>= 1.0.0, <= 5.9.2
Fixed in
5.9.3
Check
npm ls devalue

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Evaluating 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.

Credited to elliott-with-the-longest-name-on-github.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries