CVE-2026-116584: Seroval `fromJSON`/`fromCrossJSON` denial of service via unvalidated array node length
seroval's `fromJSON` and `fromCrossJSON` do not check that an array node's element list is an array. A small crafted payload sets the length the decoder allocates and loops over, so an unauthenticated request can exhaust memory or hang the thread. Versions 1.4.1 through 1.6.7 are affected. Fixed in 1.6.8.
Published Oct 28, 2026 · Analysis Nov 1, 2026
What an attacker can do
The decoder takes a length from the node and uses it for both memory allocation and loop count. That length does not depend on the payload size, so a few bytes can ask for a huge array. This bypasses the fix for GHSA-66fc-rw6m-c2q6 that shipped in 1.4.1.
Two outcomes follow. A small payload can allocate enough memory to kill the process. Or it can block the thread for seconds, or without end.
The risk is highest in frameworks that decode request bodies with these functions before their own validation runs, because the attacker never reaches your checks. No authentication is needed. The impact is availability only: no data is exposed or altered.
Who is affected
seroval from 1.4.1 up to and including 1.6.7. Any service that passes untrusted input to fromJSON or fromCrossJSON is exposed. Versions before 1.4.1 are outside this advisory's range. Check your direct and transitive copies:
npm ls serovalseroval
- Ecosystem
- npm
- Affected
- >= 1.4.1, <= 1.6.7
- Fixed in
- 1.6.8
- Check
npm ls seroval
How to fix it
Upgrade to [email protected].
npm install [email protected]The deserializer now rejects any node whose element list is not an array and throws SerovalMalformedNodeError. The advisory lists no workaround. For transitive copies, update the parent framework or pin the version with overrides.
How to tell if you were hit
Watch for processes killed for out-of-memory, sudden heap growth, or event-loop stalls on endpoints that decode serialized bodies, especially after a tiny request. The advisory gives no log signature. After upgrading, rejected payloads raise SerovalMalformedNodeError; alert on it, since legitimate clients should never send such nodes. Check lockfiles for seroval between 1.4.1 and 1.6.7.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
fromJSON and fromCrossJSON did not check that an array node's element list is an array. A small crafted payload could set the length the decoder used. That length controlled how much memory was allocated and how many times the decoder looped, and it did not depend on the size of the payload.
Impact
A service that passes untrusted input to fromJSON or fromCrossJSON can be made unavailable by an unauthenticated request.
- A small payload can allocate enough memory to end the process.
- A small payload can block the thread for seconds, or without end.
This affects any framework that decodes request bodies with these functions before its own validation runs.
This issue is a bypass of the fix for GHSA-66fc-rw6m-c2q6 in 1.4.1.
Patches
Fixed in [email protected]. The deserializer now rejects any node whose element list is not an array, and throws SerovalMalformedNodeError.
Workarounds
None. Upgrade to 1.6.8.
Credited to llegomark.
Questions
- Which seroval versions does CVE-2026-116584 affect?
From 1.4.1 up to and including 1.6.7. The patched release is 1.6.8.
- Can the attacker crash the process, or only slow it?
Both. The advisory says a small payload can allocate enough memory to end the process, or block the thread for seconds or indefinitely.
- How does this relate to the 1.4.1 fix?
It bypasses it. Version 1.4.1 fixed GHSA-66fc-rw6m-c2q6, but the array node's element list was still not checked to be an array.
- Is there a workaround?
The advisory lists none. Upgrade to seroval 1.6.8, which makes the deserializer reject non-array element lists with SerovalMalformedNodeError.
References
Read for this analysis:
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-116580
Seroval: Deserialization invokes attacker-chosen callables: AsyncIteratorFactoryInstance calls source.on(listener) without type check
high7.3Oct 28, 2026CVE-2026-116581
Seroval: fromJSON deserializer trusts node-supplied array length and sequence doneAt (unauthenticated event-loop DoS)
high7.5Oct 28, 2026CVE-2026-116582
Seroval: Script injection through RegExp sources in serialized output
medium4.7Oct 28, 2026CVE-2026-116583
Seroval: Code injection through a typed array's own constructor property
medium5.3Oct 28, 2026CVE-2026-104845
Seroval: Memory exhaustion via unchecked TypedArray length in JSON deserialization
high7.5Oct 5, 2026CVE-2026-104846
Seroval: `fromJSON()` Promise thenable assimilation invokes plugin-produced callables (bypass of GHSA-mv8w-475r-vwqw)
critical9.8Oct 5, 2026
