Cpe:2.3:a:seroval:seroval:*:*:*:*:*:node.js:*:* - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/cpes/cpe2.3aserovalserovalnode.js/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioTue, 06 Oct 2026 00:45:14 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgDenial of Service via Unchecked TypedArray Length in Serovalhttps://feed.craftedsignal.io/briefs/2026-10-seroval-dos/Tue, 06 Oct 2026 00:45:14 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-seroval-dos/The Seroval library is vulnerable to unauthenticated memory and CPU exhaustion due to an unchecked TypedArray length property during JSON deserialization, leading to event loop starvation.The Seroval library (versions 1.6.2 and earlier) contains a critical vulnerability in the deserializeTypedArray and fromCrossJSON functions, identified as CVE-2026-104845. The library fails to validate the source node when casting to an ArrayBuffer, specifically failing to bound the element count during deserialization. By supplying a specially crafted JSON payload containing a large integer in the length property, an attacker can trigger massive synchronous memory allocations. Because this process occurs within the event loop, it causes immediate service-wide resource exhaustion and denial of service. Unlike the DataView implementation which properly throws an error, the TypedArray handling remains susceptible to this primitive. This vulnerability impacts any service utilizing Seroval to process untrusted JSON inputs.

Impact

Successful exploitation results in unauthenticated denial of service by starving the application event loop. This leads to high CPU utilization and potential process crashes due to memory exhaustion. The impact is limited to availability; there is no identified risk to confidentiality or integrity. Any application environment utilizing Seroval to deserialize external input is at risk.

Recommendation

  1. Upgrade the Seroval package to a patched version (beyond 1.6.2) immediately upon release by the maintainers.
  2. Implement request size limiting at the API gateway or proxy level to prevent the ingestion of excessively large or malicious JSON payloads before they reach the deserialization layer.
  3. Validate incoming JSON structure schema-side before passing payloads to the Seroval fromJSON or fromCrossJSON methods.
  4. Monitor server resource metrics (CPU and Heap memory) for sudden, synchronous spikes that correlate with incoming POST requests to identify potential exploitation attempts.
]]>lowadvisorydenial-of-servicevulnerabilitydeserialization