Live › vulnerability › CVE-2026-116583
Go to dashboardSeroval versions 1.6.0 through 1.6.10 build JavaScript output using a constructor name read from a typed array property that can be overridden. If application code copies untrusted properties onto a typed array and serializes it, an attacker's name is written as executable JavaScript that runs in the receiving page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 21:20 UTC. All times on this page are UTC.
Applications that use Seroval 1.6.0 through 1.6.10 and let untrusted input add properties to typed arrays before serialization are exposed. Projects that only serialize trusted data, or that do not use Seroval's JavaScript-output APIs, are unlikely to be affected.
No product ranges from the sources yet.
npm ls seroval in the project and look for any version from 1.6.0 through 1.6.10.serialize, crossSerialize, Serializer or compileJSON.seroval to 1.6.11 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. From 1.6.0 until 1.6.11, the JavaScript-output APIs derive a typed array's constructor name from a property on the value that can be replaced by an own constructor property. When application code copies untrusted properties onto a typed array and then passes it to serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, Serializer, or compileJSON, the attacker-controlled name is written as executable JavaScript and can run in the page receiving the output. This issue is fixed in version 1.6.11.
This page as .md · .json · in your agent: get_signal("CVE-2026-116583")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.