● npm package
devalue
Devalue has 16 security advisories. The newest release any of them names as the fix is 5.9.3.
As of , devalue has 16 security advisories. The newest release any of them names as the fix is 5.9.3.
Your version, and the version to upgrade to
| If you run | Upgrade to | Advisories |
|---|---|---|
| Before 5.9.3 | 5.9.3 | 16 advisories |
Security advisories, newest first
| Advisory | What it is | Affects | Fixed in | Published |
|---|---|---|---|---|
| CVE-2026-92708GHSA-j22f-vq7h-c4qm | devalue: `stringify`/`uneval` serialize shared memoryHigh severity | From 5.1.0 before 5.9.3 | 5.9.3 | |
| CVE-2026-123566GHSA-hx4r-w6wj-j8fg | devalue: Residual sparse-array CPU amplification in unevalModerate severity | Before 5.9.3 | 5.9.3 | |
| CVE-2026-123565GHSA-mcm9-63f2-9j32 | devalue: Repeated primitive strings cause quadratic expansion in unevalHigh severity | Before 5.9.3 | 5.9.3 | |
| CVE-2026-123564GHSA-wf3x-273g-mvxv | devalue: Sparse arrays emitted by uneval cause eager allocation when evaluatedLow severity | From 1.0.0 before 5.9.3 | 5.9.3 | |
| CVE-2026-123563GHSA-r9w8-h9r3-54w4 | devalue: Custom ArrayBuffer revivers can bypass typed-array allocation validationHigh severity | Before 5.9.3 | 5.9.3 | |
| CVE-2026-123562GHSA-x5rw-q4pp-hg5g | devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promiseHigh severity | From 5.8.0 before 5.9.3 | 5.9.3 | |
| CVE-2026-123561GHSA-4q55-j62x-fr9h | devalue: Malformed null-prototype object keys bypass __proto__ rejection via property-key coercionModerate severity | Before 5.9.3 | 5.9.3 | |
| CVE-2026-81176GHSA-9rgm-9g3h-6x36 | Svelte devalue: DoS via malformed inputModerate severity | Before 5.9.2 | 5.9.2 | |
| CVE-2026-42570GHSA-77vg-94rm-hx3p | Svelte devalue: DoS via sparse array deserializationHigh severity | From 5.6.3 before 5.8.1 | 5.8.1 | |
| CVE-2026-123567GHSA-mwv9-gp5h-frr4 | Sveltejs devalue's `devalue.parse` and `devalue.unflatten` emit objects with `__proto__` own propertiesLow severity | From 4.0.0 before 5.6.4 | 5.6.4 | |
| CVE-2026-30226GHSA-cfw5-2vxh-hr84 | devalue has prototype pollution in devalue.parse and devalue.unflattenModerate severity | Before 5.6.4 | 5.6.4 | |
| CVE-2026-123569GHSA-33hq-fvwr-56pm | devalue affected by CPU and memory amplification from sparse arraysLow severity | Before 5.6.3 | 5.6.3 | |
| CVE-2026-123568GHSA-8qm3-746x-r74r | devalue `uneval`ed code can create objects with polluted prototypes when `eval`edLow severity | Before 5.6.3 | 5.6.3 | |
| CVE-2026-22775GHSA-g2pg-6438-jwpf | devalue vulnerable to denial of service due to memory/CPU exhaustion in devalue.parseHigh severity | From 5.1.0 before 5.6.2 | 5.6.2 | |
| CVE-2026-22774GHSA-vw5p-8cq8-m7mv | Devalue is vulnerable to denial of service due to memory exhaustion in devalue.parseHigh severity | From 5.3.0 before 5.6.2 | 5.6.2 | |
| CVE-2025-57820GHSA-vj54-72f3-p5jv | devalue prototype pollution vulnerabilityHigh severity | Before 5.3.2 | 5.3.2 |
Other npm packages
- signalk-server17 advisories
- @haxtheweb/haxcms-nodejs16 advisories
- mermaid16 advisories
- angular15 advisories
Sources
- Package advisories from the GitHub Advisory Database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0