lxsmnsyc seroval up to 1.4.0 Maximum Call serialization depthLimit allocation of resources

Summaryinfo

A vulnerability identified as problematic has been detected in lxsmnsyc seroval up to 1.4.0. Impacted is the function serialization of the component Maximum Call Handler. The manipulation of the argument depthLimit leads to allocation of resources. This vulnerability is documented as CVE-2026-24006. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in lxsmnsyc seroval up to 1.4.0. This issue affects the function serialization of the component Maximum Call Handler. The manipulation of the argument depthLimit with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:

Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, serialization of objects with extreme depth can exceed the maximum call stack limit. In version 1.4.1, Seroval introduces a `depthLimit` parameter in serialization/deserialization methods. An error will be thrown if the depth limit is reached.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-24006 since 01/19/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.

Upgrading to version 1.4.1 eliminates this vulnerability. Applying the patch ce9408ebc87312fcad345a73c172212f2a798060 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• lxsmnsyc

Name

• seroval

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4.0

License

• open-source

Website

• Product: https://github.com/lxsmnsyc/seroval/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion