seroval (npm) has 13 known vulnerabilities, the worst rated CRITICAL. Upgrade to 1.6.11 or later to clear all of them. No malicious-package signal is recorded.
A fulfilled Promise node deserialized by fromJSON() can trigger unintended invocation of a plugin-produced callable through native ECMAScript thenable…
CyberXYZ does not call a package safe in absolute terms. It records 13 known vulnerabilities for seroval (npm), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Does seroval have known vulnerabilities?
Yes. CyberXYZ records 13 known vulnerabilities for seroval (npm), the worst rated CRITICAL. These include GHSA-p6vx-979v-rg4c, GHSA-mv8w-475r-vwqw, GHSA-97r2-qh9m-474h, GHSA-7rv5-mrxv-xcr9, GHSA-wp97-x4hv-qvhp.
Which version of seroval should I use?
1.6.11 or later clears every advisory recorded for seroval (npm). Check the release you pick before installing it.
How do I check seroval before installing?
Search seroval in CyberXYZ Check at https://cyberxyz.io/check?q=seroval. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 10:14 UTC. The most recent advisory here was published 2026-10-28. Updated continuously from NVD, GHSA, OSV and CNA feeds.