GHSA-x5rw-q4pp-hg5g

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

This page contains facts from public vulnerability sources. Check the original advisory before updating.

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.

CVSS 8.2 · High · Fix available

Published

2026-10-01T15:15:13Z

Updated

2026-10-01T15:30:10.729813749Z

Stack: node

Check your server →