Quick answers
- Is CVE-2026-104845 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104845 being exploited in the wild.
- How severe is CVE-2026-104845?
- High severity, with a CVSS score of 7.5, published 2 October 2026.
- Which products and versions are affected?
- Lxsmnsyc Seroval before 1.6.3; seroval (npm) <= 1.6.2, SEMVER:introduced=0,fixed=1.6.3.
- Is there a fix for CVE-2026-104845?
- Yes. seroval (npm): upgrade to 1.6.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104845 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-104845?
- 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.3 or later
npm install seroval@1.6.3
Technical details
The deserializeTypedArray function in fromJSON and fromCrossJSON fails to validate the element count of serialized TypedArray structures, trusting a source value as an ArrayBuffer without checking byteLength. An attacker provides a small JSON object with a large length field, causing the TypedArray constructor to synchronously allocate the specified number of elements, exhausting memory or CPU and starving the event loop. The offset validation does not catch this because source.byteLength is undefined in the crafted input.
Affected products
- lxsmnsyc Seroval before 1.6.3
Identifiers
- CVE-2026-104845
- GHSA-jp82-f5mq-hwhp
Timeline
- 2026-10-02: disclosed
- 2026-10-02: patched