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

> A race condition in devalue's stringifyAsync can cause unhandled rejections, potentially crashing the Node.js process under specific timing conditions.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026

## What is GHSA-x5rw-q4pp-hg5g?

GHSA-x5rw-q4pp-hg5g is a denial of service vulnerability in devalue, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

## Which versions are affected by GHSA-x5rw-q4pp-hg5g?

2 open source packages ship an affected version, including devalue.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `devalue` | npm | From 5.8.0 | 5.9.3 |
| `devalue` | npm | From 5.8.0 | 5.9.3 |

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

Upgrade devalue to 5.9.3 or later.

## Is GHSA-x5rw-q4pp-hg5g being exploited?

There is no known exploitation of GHSA-x5rw-q4pp-hg5g in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-x5rw-q4pp-hg5g and fix it if it is affected.

What it is: GHSA-x5rw-q4pp-hg5g is a denial of service vulnerability in devalue, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-x5rw-q4pp-hg5g in the wild and no public exploit code.

Affected packages and fixed versions:
- devalue (npm): affected from 5.8.0; fixed in 5.9.3
- devalue (npm): affected from 5.8.0; fixed in 5.9.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-x5rw-q4pp-hg5g/ (Markdown: https://insights.sbomify.com/GHSA-x5rw-q4pp-hg5g/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-x5rw-q4pp-hg5g

---
From sbomify Insights: https://insights.sbomify.com/GHSA-x5rw-q4pp-hg5g/
Summaries are generated and may contain mistakes; the official description above is the record.