CVE-2026-123569 · Package
NO FIX YET · SEE WHAT TO DO
The devalue npm package before 5.6.3 uses excessive CPU and memory when serializing sparse arrays with uneval or stringify. An attacker who gets a sparse array created on the server and serialized there can cause a denial of service.
first public Feb 18, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Applications that call devalue's uneval or stringify on server-side data that could contain sparse arrays created from attacker input. Projects that do not serialize data with devalue on the server, or that never let outside input create sparse arrays, are less exposed. The sources do not say which frameworks embed devalue by default.
Not affected if no-devalue-dependency, no-server-serialization
Who cares devalue, node, npm, server-side-serialization
npm ls devalue in each project.5.6.3 or later.The devalue package for npm before 5.6.3 can consume excessive CPU and memory when serializing sparse arrays with uneval or stringify. An attacker who manages to get a sparse array created on the server, which mainstream wire formats do not allow, and serialized there can cause a denial of service.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.