Resource exhaustion in Lxsmnsyc Seroval
CVE-2026-104845
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 serialized element count. An attacker can provide a small untrusted JSON object with a large length value, causing the array-like TypedArray constructor to synchronously allocate the selected number of elements and exhaust CPU or memory while starving the event loop. The offset check does not reject the crafted source because source.byteLength is undefined. DataView reaches a similar unchecked cast but throws rather than allocating, and the issue has no identified confidentiality or integrity impact. This issue is fixed in version 1.6.3.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Affected products
- Lxsmnsyc Seroval — versions < 1.6.3
Weakness classification (CWE)
References
Frequently asked questions
- What is CVE-2026-104845?
- CVE-2026-104845 is a high-severity vulnerability in Lxsmnsyc Seroval, classified under Allocation of Resources Without Limits or Throttling. CVSS score: 7.5/10. Published 2026-10-02.
- How severe is CVE-2026-104845?
- High severity. CVSS v3 base score is 7.5 out of 10.