Advisory

GHSA-x5rw-q4pp-hg5g

Also known as: CVE-2026-123562

Summary

devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise

Details

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-10-01 15:15 UTC
Modified
2026-11-08 10:56 UTC

Affected packages and fixes

devalue

npm · All systems

Affected

  • introduced 5.8.0, fixed 5.9.3 (semver)

Fixed versions

5.9.3

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences