Quick answers
- Is CVE-2026-24006 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-24006 being exploited in the wild.
- How severe is CVE-2026-24006?
- Low severity, with a CVSS score of 3.1, published 22 January 2026.
- Which products and versions are affected?
- seroval (npm) SEMVER:introduced=0,fixed=1.4.1.
- Is there a fix for CVE-2026-24006?
- Yes. seroval (npm): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-24006 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-24006?
- Check whether you run 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.4.1 or later
npm install seroval@1.4.1
Technical details
This is a stack exhaustion vulnerability (CWE-770) in Seroval's serialization/deserialization mechanism. When processing objects with extreme nesting depth, the recursive serialization logic exceeds the JavaScript call stack limit, causing a denial of service. The vulnerability affects all versions prior to 1.4.1. The attack is network-accessible and requires no privileges or user interaction—any external input passed to Seroval's serialization methods can trigger the crash. The fix introduces a configurable depthLimit parameter that throws an error when the nesting depth threshold is reached, preventing stack exhaustion. Patch is available in version 1.4.1 and later.
Affected products
- lxsmnsyc seroval <=1.4.0
Identifiers
- CVE-2026-24006
- GHSA-3j22-8qj3-26mx
Timeline
- 2026-01-22: disclosed: Advisory published
- 2026-01-21: patched: Fix released in version 1.4.1