devalue: Sparse arrays emitted by uneval cause eager allocation when evaluated
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.
GHSA-wf3x-273g-mvxv
Primary source · Revision 1
Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.
Security context
Source reference: osv:GHSA-wf3x-273g-mvxv
devalue
Source reference: /affected/0/package/name
- Affected versions
- Not stated in this record
- Fixed versions
- 5.9.3
Source reference:
/affected/0/ranges - Prerequisites
- Not stated in this record
Structured affected-version data
Original package identities and version rules from this source.
[
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "1.0.0"
},
{
"fixed": "5.9.3"
}
]
}
],
"package": {
"name": "devalue",
"purl": "pkg:npm/devalue",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-wf3x-273g-mvxv/GHSA-wf3x-273g-mvxv.json",
"last_known_affected_version_range": "<= 5.9.2"
}
}
]Publisher severity
low
Source reference: /database_specific/severity
- Event
- #61203 · Revision 1
- Added to Heist Feed
- Publisher date