GHSA-x5rw-q4pp-hg5g devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise
A race condition in devalue's stringifyAsync can cause unhandled rejections, potentially crashing the Node.js process under specific timing conditions.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-x5rw-q4pp-hg5g?
GHSA-x5rw-q4pp-hg5g is a denial of service vulnerability in devalue, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by GHSA-x5rw-q4pp-hg5g?
2 open source packages ship an affected version, including devalue.
| Package | Affected | Fixed in |
|---|---|---|
devalue npm | From 5.8.0 | 5.9.3 |
devalue npm | From 5.8.0 | 5.9.3 |
How do I fix GHSA-x5rw-q4pp-hg5g?
Upgrade devalue to 5.9.3 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is GHSA-x5rw-q4pp-hg5g being exploited?
There is no known exploitation of GHSA-x5rw-q4pp-hg5g in the wild and no public exploit code.