How severe is GHSA-33hq-fvwr-56pm?

No CVSS score has been assigned to GHSA-33hq-fvwr-56pm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-33hq-fvwr-56pm?

GHSA-33hq-fvwr-56pm affects the following packages: devalue (npm). Ecosystems affected: npm.

How do I fix GHSA-33hq-fvwr-56pm?

Update devalue to 5.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33hq-fvwr-56pm is resolved across your whole dependency graph.

How do I detect GHSA-33hq-fvwr-56pm 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-33hq-fvwr-56pm 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.

How does O3 Security protect against GHSA-33hq-fvwr-56pm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-33hq-fvwr-56pm can be triaged on real exposure rather than presence alone.

Is GHSA-33hq-fvwr-56pm actively exploited in the wild?

No public exploit code has been indexed for GHSA-33hq-fvwr-56pm 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-33hq-fvwr-56pm published, and has it been updated?

GHSA-33hq-fvwr-56pm was published on February 19, 2026 and was last updated on February 22, 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

GHSA-33hq-fvwr-56pm — devalue

Fix: sveltejs/devalue@819f1ac

GHSA-33hq-fvwr-56pm is a security vulnerability in devalue. A fix is available for devalue — see the affected versions and patch details below.

devalue affected by CPU and memory amplification from sparse arrays

Published

Feb 19, 2026

Updated

Feb 22, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 22, 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.

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

devaluenpm

9.8Mdownloads / week

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`devalue`	all versions	5.6.3`npm install devalue@5.6.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.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-33hq-fvwr-56pm 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-33hq-fvwr-56pm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-33hq-fvwr-56pm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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`.

O3 Security · Impact-Aware SCA

Is GHSA-33hq-fvwr-56pm in your dependencies?

O3 Security finds GHSA-33hq-fvwr-56pm across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works