High · CVSS 7.5CVE-2026-104845

Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization

Answer in brief

CVE-2026-104845 records a High severity (CVSS 7.5) vulnerability in Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization. The current sources do not mark it as known exploited. The current feed maps lxsmnsyc/seroval (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 2, 2026Updated Oct 2, 2026Source checked Oct 2, 2026First seen by HOL Oct 2, 2026Material review Oct 2, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps lxsmnsyc/seroval (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
lxsmnsyc/serovalgeneric	<1.6.3	1.6.3

Recommended response

Check inventory. Check lockfiles and deployed manifests for lxsmnsyc/seroval.
Review the reported fix. Update lxsmnsyc/seroval to 1.6.3 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 2, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 2, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.