Quick answers
- Is CVE-2026-116583 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116583 being exploited in the wild.
- How severe is CVE-2026-116583?
- Medium severity, with a CVSS score of 4, published 26 October 2026.
- Which products and versions are affected?
- Lxsmnsyc Seroval 1.6.0 to 1.6.10; seroval (npm) >= 1.6.0, < 1.6.11, SEMVER:introduced=1.6.0,fixed=1.6.11.
- Is there a fix for CVE-2026-116583?
- Yes. seroval (npm): upgrade to 1.6.11 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116583 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116583?
- Check whether you run Lxsmnsyc Seroval or seroval (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- seroval (npm): upgrade to 1.6.11 or later
npm install seroval@1.6.11
Technical details
The vulnerability is a code injection flaw in Seroval's typed array serialization. When serializing typed arrays, the library reads the constructor name from value.constructor.name, which can be replaced by an attacker-supplied own property. This attacker-controlled name is written directly into the output JavaScript code after the `new` keyword, allowing arbitrary code injection. The flaw affects serialize, serializeAsync, crossSerialize, crossSerializeAsync, crossSerializeStream, and the Serializer and compileJSON APIs.
Affected products
- lxsmnsyc Seroval 1.6.0 to 1.6.10
Identifiers
- CVE-2026-116583
- GHSA-f86p-h4j2-7qgj
Timeline
- 2026-10-26: disclosed
- 2026-10-18: patched