Devalue 5.8.0 before 5.9.3 Denial of Service via stringifyAsync Unhandled Rejection
cve-program · CVE-2026-123562
Publisheddevalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller catches the returned promise. An attacker able to influence the timing or failure of serialized asynchronous values can terminate the Node.js process.
Read the publisher's advisoryeuvd · EUVD-2026-119447
Publisheddevalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller catches the returned promise. An attacker able to influence the timing or failure of serialized asynchronous values can terminate the Node.js process.
Read the publisher's advisorynvd · CVE-2026-123562
Publisheddevalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, even if the caller catches the returned promise. An attacker able to influence the timing or failure of serialized asynchronous values can terminate the Node.js process.
Read the publisher's advisoryosv · GHSA-x5rw-q4pp-hg5g
PublishedWhen 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-123562 · CVE overview and exploitation status
cve-program · CVE-2026-123562
- https://github.com/sveltejs/devalue/security/advisories/GHSA-x5rw-q4pp-hg5g
- https://www.vulncheck.com/advisories/devalue-5.8.0-before-5.9.3-denial-of-service-via-stringifyasync-unhandled-rejection
euvd · EUVD-2026-119447
- https://github.com/sveltejs/devalue/security/advisories/GHSA-x5rw-q4pp-hg5g
- https://www.vulncheck.com/advisories/devalue-5.8.0-before-5.9.3-denial-of-service-via-stringifyasync-unhandled-rejection
nvd · CVE-2026-123562
- https://github.com/sveltejs/devalue/security/advisories/GHSA-x5rw-q4pp-hg5g
- https://www.vulncheck.com/advisories/devalue-5.8.0-before-5.9.3-denial-of-service-via-stringifyasync-unhandled-rejection
osv · GHSA-x5rw-q4pp-hg5g
Related changes
Linked by CVE identifier- devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, eve… · Advisory content revised · 14 Nov 2026
- devalue (sveltejs/devalue) 5.8.0 before 5.9.3 contains an unhandled promise rejection in stringifyAsync: when serializing multiple promises, a later promise rejecting before an earlier one settles leaves an internal rejection unhandled, eve… · Advisory content revised · 10 Nov 2026
- Devalue 5.8.0 before 5.9.3 Denial of Service via stringifyAsync Unhandled Rejection · Newly collected advisory · 8 Nov 2026
- devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise · Advisory content revised · 8 Nov 2026