devalue: Repeated primitive strings cause quadratic expansion in unevalGHSA-mcm9-63f2-9j32
Fix: sveltejs/devalue@84f6f67GHSA-mcm9-63f2-9j32 is a security vulnerability in devalue. A fix is available for devalue — see the affected versions and patch details below.
Real-World Exposure
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.
devaluenpmDescription
Under very constrained circumstances, data that was parsed and then passed to uneval could turn a small payload into a very large serialized string.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | devalue | all versions | 5.9.3npm install devalue@5.9.3 |
Detection & mitigation playbook
Open-source dependencyDetect
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-mcm9-63f2-9j32 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
Is GHSA-mcm9-63f2-9j32 in your dependencies?
Find it across npm, including transitive dependencies.