Summary
devalue: Sparse arrays emitted by uneval cause eager allocation when evaluated
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.
Impact
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-WF3X-273G-MVXV? GHSA-WF3X-273G-MVXV is a low-severity uncontrolled resource consumption vulnerability in devalue (npm), affecting versions >= 1.0.0, <= 5.9.2. It is fixed in 5.9.3. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- Which versions of devalue are affected by GHSA-WF3X-273G-MVXV? devalue (npm) versions >= 1.0.0, <= 5.9.2 is affected.
- Is there a fix for GHSA-WF3X-273G-MVXV? Yes. GHSA-WF3X-273G-MVXV is fixed in 5.9.3. Upgrade to this version or later.
- Is GHSA-WF3X-273G-MVXV exploitable, and should I be worried? Whether GHSA-WF3X-273G-MVXV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-WF3X-273G-MVXV is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-WF3X-273G-MVXV? Upgrade
devalueto 5.9.3 or later.