Lxsmnsyc vulnerabilities
We track 11 vulnerabilities in Lxsmnsyc products. 11 are rated high or critical, and none are known to be exploited. The most recent was published on October 26, 2026.
Latest Lxsmnsyc vulnerabilities
- 7.5 High severity
seroval: Allocation of Resources Without Limits or Throttling
Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. From 1.4.1 until 1.6.8, fromJSON and fromCrossJSON do not require an array node's element list to be an actual array. A small crafted payload
- 7.5 High severity
seroval: Loop with Unreachable Exit Condition
Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.6.8, fromJSON and fromCrossJSON do not validate a sequence node's done index. A crafted done index can create an iterator that nev
- 7.3 High severity
seroval: Deserialization of Untrusted Data
Seroval facilitates JavaScript value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.6.8, fromJSON rebuilds an AsyncIteratorFactoryInstance by calling source.on(listener) without requiring source to be a genuine int
- 9.8 Critical severity
seroval: Access of Resource Using Incompatible Type
Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. From 0.12.0 until 1.6.2, fromJSON deserialization of a fulfilled Promise control node can pass a plugin-produced callable-bearing thenable to a nativ
- 7.5 High severity
seroval: Allocation of Resources Without Limits or Throttling
Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.6.3, deserializeTypedArray in fromJSON and fromCrossJSON trusts a deserialized source value as an ArrayBuffer and does not bound the seria
- 9.8 Critical severity
seroval: Deserialization of Untrusted Data
Seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. Prior to 1.5.3, seroval.fromJSON() allows attacker-controlled JSON Promise control nodes to operate on values from the general deserialization refere
- 7.5 High severity
seroval: Allocation of Resources Without Limits or Throttling
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 introduce
- 7.5 High severity
seroval: Allocation of Resources Without Limits or Throttling
seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, overriding encoded array lengths by replacing them with an excessively large value causes the deserialization process to
- 7.5 High severity
seroval: Inefficient Regular Expression Complexity
seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 0.2.0 through 1.4.0, overriding RegExp serialization with extremely large patterns can exhaust JavaScript runtime memory during deseriali
- 7.5 High severity
seroval: Deserialization of Untrusted Data
seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, improper input handling in the JSON deserialization component can lead to arbitrary JavaScript code execution. Exploitat
- 9.8 Critical severity
seroval: Improperly Controlled Modification of Object Prototype Attributes
seroval facilitates JS value stringification, including complex structures beyond JSON.stringify capabilities. In versions 1.4.0 and below, due to improper input validation, a malicious object key can lead to prototype pollution during JSON deserialization. Th