GHSA-x5rw-q4pp-hg5g

Source

https://github.com/advisories/GHSA-x5rw-q4pp-hg5g

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-x5rw-q4pp-hg5g/GHSA-x5rw-q4pp-hg5g.json

JSON Data

https://api.osv.dev/v1/vulns/GHSA-x5rw-q4pp-hg5g

Downstream

CLSA-2026-1790888210

Published

2026-10-01T15:15:13Z

Modified

2026-10-01T15:30:10Z

Severity

8.2 (High) CVSS_V4 - CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CVSS Calculator

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.

Database specific

{
    "cwe_ids":  [
        "CWE-248",
        "CWE-755"
    ],
    "github_reviewed":  true,
    "github_reviewed_at":  "2026-10-01T15:15:13Z",
    "nvd_published_at":  null,
    "severity":  "HIGH"
}

References

Affected packages

npm / devalue

Package

Name: devalue; View open source insights on deps.dev
Purl: pkg:npm/devalue

Affected ranges

Type: SEMVER
Events: Introduced

5.8.0

Fixed

5.9.3

Database specific

last_known_affected_version_range

"<= 5.9.2"

source

"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-x5rw-q4pp-hg5g/GHSA-x5rw-q4pp-hg5g.json"