Quick answers
- Is CVE-2026-116581 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116581 being exploited in the wild.
- How severe is CVE-2026-116581?
- High severity, with a CVSS score of 7.5, published 26 October 2026.
- Which products and versions are affected?
- Lxsmnsyc Seroval before 1.6.8; seroval (npm) <= 1.6.7, SEMVER:introduced=0,fixed=1.6.8.
- Is there a fix for CVE-2026-116581?
- Yes. seroval (npm): upgrade to 1.6.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116581 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116581?
- 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.8 or later
npm install seroval@1.6.8
Technical details
The vulnerability exists in the fromJSON and fromCrossJSON deserialization functions prior to version 1.6.8, which fail to validate a sequence node's done index during deserialization. An attacker can craft a sequence with a malicious done index that produces an iterator object that never completes iteration. This leads to an infinite loop when application code consumes the iterator, blocking the event loop and exhausting process memory. The fix validates sequence indices during deserialization to prevent this condition.
Affected products
- lxsmnsyc Seroval before 1.6.8
Identifiers
- CVE-2026-116581
- GHSA-97r2-qh9m-474h
Timeline
- 2026-10-26: disclosed
- 2026-09-29: patched: Version 1.6.8 released