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

GHSA-x5rw-q4pp-hg5g: devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

highCVSS 4.0 8.2

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.

Published Oct 1, 2026

Affected packages

devalue

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

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

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