GHSA-8qm3-746x-r74r: devalue `uneval`ed code can create objects with polluted prototypes when `eval`ed
Under certain circumstances, unevaling untrusted data can produce output code that will create objects with polluted prototypes when later evaled, meaning the output data can be a different shape from the input data.
Published Feb 19, 2026
Affected packages
devalue
- Ecosystem
- npm
- Affected
- <= 5.6.2
- Fixed in
- 5.6.3
- Check
npm ls devalue
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Under certain circumstances, unevaling untrusted data can produce output code that will create objects with polluted prototypes when later evaled, meaning the output data can be a different shape from the input data.
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 entriesCVE-2026-92708
devalue: `stringify`/`uneval` serialize shared memory
high7.5Oct 1, 2026GHSA-4q55-j62x-fr9h
devalue: Malformed null-prototype object keys bypass __proto__ rejection via property-key coercion
medium6.3Oct 1, 2026GHSA-hx4r-w6wj-j8fg
devalue: Residual sparse-array CPU amplification in uneval
medium6.3Oct 1, 2026GHSA-mcm9-63f2-9j32
devalue: Repeated primitive strings cause quadratic expansion in uneval
high8.2Oct 1, 2026GHSA-r9w8-h9r3-54w4
devalue: Custom ArrayBuffer revivers can bypass typed-array allocation validation
high8.2Oct 1, 2026GHSA-wf3x-273g-mvxv
devalue: Sparse arrays emitted by uneval cause eager allocation when evaluated
low2.3Oct 1, 2026
