Skip to main content
VulnerabilityPublished

CVE-2026-116583: Seroval · Code injection through a typed array's own constructor property

Affects serovalSource GCVE Database

0
Authoritative record:CVE-2026-116583· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.6.11 when convenient.

Data as of 28 Oct 2026, 22:28 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.6.11
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade seroval to 1.6.11.

Affected software

ProductAffectedFixed in
npmserovalAffected
  • >=1.6.0 <1.6.11
Fixed in
  • 1.6.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade seroval to version 1.6.11 or later, where the vulnerability is fixed by using the typed array's internal type for constructor name resolution. If upgrading is not possible, avoid copying properties from untrusted objects onto typed arrays or remove any own constructor property from typed arrays before serialization. The compactArrayBufferViews option also mitigates the issue by throwing a TypeError instead of writing code when the constructor name is invalid.

Description

Seroval versions 1.6.0 through 1.6.10 contain a vulnerability where typed arrays that have an own constructor property set from untrusted data can lead to code injection during serialization. This occurs because the constructor name is read from a mutable property on the typed array rather than its internal type, allowing arbitrary code to be serialized. The issue is fixed in version 1.6.11. The vulnerability requires unusual conditions where properties from untrusted objects are copied onto typed arrays.

References

Community reviews

Loading reviews…