How severe is GHSA-x5rw-q4pp-hg5g?

No CVSS score has been assigned to GHSA-x5rw-q4pp-hg5g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-x5rw-q4pp-hg5g?

GHSA-x5rw-q4pp-hg5g affects the following packages: devalue (npm). Ecosystems affected: npm.

How do I fix GHSA-x5rw-q4pp-hg5g?

Update devalue to 5.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5rw-q4pp-hg5g is resolved across your whole dependency graph.

How do I detect GHSA-x5rw-q4pp-hg5g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for devalue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-x5rw-q4pp-hg5g if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-x5rw-q4pp-hg5g actively exploited in the wild?

No public exploit code has been indexed for GHSA-x5rw-q4pp-hg5g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-x5rw-q4pp-hg5g published, and has it been updated?

GHSA-x5rw-q4pp-hg5g was published on October 1, 2026 and was last updated on October 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

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

Fix: sveltejs/devalue@dae8153

GHSA-x5rw-q4pp-hg5g is a security vulnerability in devalue. A fix is available for devalue — see the affected versions and patch details below.

Published

Oct 1, 2026

Updated

Oct 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 1, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

384other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

devaluenpm

11.8Mdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`devalue`	≥ 5.8.0&&< 5.9.3	5.9.3`npm install devalue@5.9.3`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for devalue, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update devalue to 5.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x5rw-q4pp-hg5g is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-x5rw-q4pp-hg5g in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works