Quick answers
- Is CVE-2026-116580 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116580 being exploited in the wild.
- How severe is CVE-2026-116580?
- High severity, with a CVSS score of 7.3, published 26 October 2026.
- Which products and versions are affected?
- Alexis Munsayac Seroval before 1.6.8; seroval (npm) <= 1.6.7, SEMVER:introduced=0,fixed=1.6.8.
- Is there a fix for CVE-2026-116580?
- 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-116580 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-116580?
- Check whether you run Alexis Munsayac 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 is an incomplete fix (CVE-2026-59940) where fromJSON rebuilds AsyncIteratorFactoryInstance by calling source.on(listener) without validating that source is a genuine internal stream. An attacker can reuse identifier slots in untrusted Seroval input to pass a malicious callable or object with an on method, triggering plugin-supplied code. The fix in 1.6.8 now uses instanceof checks and real classes instead of marker properties to prevent identity spoofing.
Affected products
- Alexis Munsayac Seroval before 1.6.8
Identifiers
- CVE-2026-116580
- GHSA-7rv5-mrxv-xcr9
Timeline
- 2026-10-26: disclosed