devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise
When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned `stringifyAsync` promise. Under Node's default unhandled-rejection behavior this can terminate the process. Applications whose asynchronous failures/timing can be influenced by requests are potentially exposed. This is essentially impossible to exploit, and is much more likely to surface as a developer-introduced bug.
GHSA-x5rw-q4pp-hg5g
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-x5rw-q4pp-hg5g
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": "5.8.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-x5rw-q4pp-hg5g/GHSA-x5rw-q4pp-hg5g.json",
"last_known_affected_version_range": "<= 5.9.2"
}
}
]Publisher severity
high
Source reference: /database_specific/severity
- Event
- #61180 · Revision 1
- Added to Heist Feed
- Publisher date