GHSA-33hq-fvwr-56pm devalue affected by CPU and memory amplification from sparse arrays
Not scored
Published
Check this codebase for GHSA-33hq-fvwr-56pm and fix it if it is affected.
What it is: GHSA-33hq-fvwr-56pm is a denial of service vulnerability in devalue, published on 19 Feb 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-33hq-fvwr-56pm in the wild and no public exploit code.
Affected packages and fixed versions:
- devalue (npm): affected all versions; fixed in 5.6.3
- devalue (npm): affected all versions; fixed in 5.6.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-33hq-fvwr-56pm/ (Markdown: https://insights.sbomify.com/GHSA-33hq-fvwr-56pm/index.md)
An attacker could cause server-side CPU and memory exhaustion by triggering serialization of sparse arrays, leading to denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-33hq-fvwr-56pm?
GHSA-33hq-fvwr-56pm is a denial of service vulnerability in devalue, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Under certain circumstances, serializing sparse arrays using
uneval or stringify could cause CPU and/or memory exhaustion. When this occurs on the server, it results in a DoS. This is extremely difficult to take advantage of in practice, as an attacker would have to manage to create a sparse array on the server — which is impossible in every mainstream wire format — and then that sparse array would have to be run through uneval or stringify.Which versions are affected by GHSA-33hq-fvwr-56pm?
2 open source packages ship an affected version, including devalue.
| Package | Affected | Fixed in |
|---|---|---|
devalue npm | All versions | 5.6.3 |
devalue npm | All versions | 5.6.3 |
How do I fix GHSA-33hq-fvwr-56pm?
Upgrade devalue to 5.6.3 or later.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is GHSA-33hq-fvwr-56pm being exploited?
There is no known exploitation of GHSA-33hq-fvwr-56pm in the wild and no public exploit code.