Description
A type confusion issue in seroval.fromJSON() allowed attacker-controlled JSON input to cause Promise control nodes to operate on values from the general deserialization reference table without first verifying that those values were genuine internal promise resolver records.
Recommendation
Update the seroval package to the latest compatible version. Followings are version details:
- Affected version(s): <= 1.5.2
- Patched version(s): 1.5.3
References
Could your website be exposed too?
SmartScanner can check your website for seroval: `seroval.fromJSON()` Promise resolver type confusion invokes attacker-controlled methods during deserialization and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) witho - CVE-2026-116580
- Seroval: `fromJSON()` Promise thenable assimilation invokes plugin-produced callables (bypass of GHSA-mv8w-475r-vwqw) - CVE-2026-104846
- Credential confusion in @sigstore/oci can leak registry credentials to an attacker-controlled registry - CVE-2026-59891
- xmldom: XML injection via unsafe CDATA serialization allows attacker-controlled markup insertion - xmldom - CVE-2026-34601


