How severe is GHSA-wf3x-273g-mvxv?

No CVSS score has been assigned to GHSA-wf3x-273g-mvxv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wf3x-273g-mvxv?

GHSA-wf3x-273g-mvxv affects the following packages: devalue (npm). Ecosystems affected: npm.

How do I fix GHSA-wf3x-273g-mvxv?

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

How do I detect GHSA-wf3x-273g-mvxv 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-wf3x-273g-mvxv if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-wf3x-273g-mvxv actively exploited in the wild?

No public exploit code has been indexed for GHSA-wf3x-273g-mvxv 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-wf3x-273g-mvxv published, and has it been updated?

GHSA-wf3x-273g-mvxv 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: Sparse arrays emitted by uneval cause eager allocation when evaluatedGHSA-wf3x-273g-mvxv

Fix: sveltejs/devalue@6861dbb

GHSA-wf3x-273g-mvxv 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.

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

devaluenpm

11.0Mdownloads / week

Description

Evaluating legitimate uneval output for a sparse array can allocate memory proportional to its declared length. A tiny serialized value can therefore cause large memory allocation in a consuming browser/runtime. This occurs during evaluation of generated code, not in default parse sparse-array construction.

You would only be affected by this if you were serializing very large sparse arrays and then evaluating the results. In the general use case for uneval of sending data to the client, the worst that could happen is the browser tab running out of memory.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`devalue`	≥ 1.0.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-wf3x-273g-mvxv is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Evaluating legitimate `uneval` output for a sparse array can allocate memory proportional to its declared length. A tiny serialized value can therefore cause large memory allocation in a consuming browser/runtime. This occurs during evaluation of generated code, not in default `parse` sparse-array construction. You would only be affected by this if you were serializing very large sparse arrays and then evaluating the results. In the general use case for `uneval` of sending data to the client, the worst that could happen is the browser tab running out of memory.

O3 Security · Impact-Aware SCA

Is GHSA-wf3x-273g-mvxv in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works