CVE-2026-23736: seroval Affected by Prototype Pollution via JSON Deserialization
Due to improper input validation, a malicious object key can lead to prototype pollution during JSON deserialization. This affects only JSON deserialization functionality. As there is no known workaround, please upgrade to the latest version.
Published Jan 21, 2026 · Updated Jan 22, 2026
Affected packages
seroval
- Ecosystem
- npm
- Affected
- < 1.4.1
- Fixed in
- 1.4.1
- Check
npm ls seroval
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Due to improper input validation, a malicious object key can lead to prototype pollution during JSON deserialization. This affects only JSON deserialization functionality.
As there is no known workaround, please upgrade to the latest version.
Credited to lxsmnsyc, tweidinger.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-116580
Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) without type check
high7.3Oct 28, 2026CVE-2026-116581
Seroval: fromJSON deserializer trusts node-supplied array length and sequence doneAt (unauthenticated event-loop DoS)
high7.5Oct 28, 2026CVE-2026-116582
Seroval: Script injection through RegExp sources in serialized output
medium4.7Oct 28, 2026CVE-2026-116583
Seroval: Code injection through a typed array's own constructor property
medium5.3Oct 28, 2026CVE-2026-116584
Seroval `fromJSON`/`fromCrossJSON` denial of service via unvalidated array node length
high7.5Oct 28, 2026CVE-2026-104845
Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization
high7.5Oct 5, 2026
