CVE-2026-116584

Seroval fromJSON/fromCrossJSON denial of service via unvalidated array node length

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.

Workarounds

None. Upgrade to 1.6.8.

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.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2026-116584 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.8); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

Fixed in [email protected]. The deserializer now rejects any node whose element list is not an array, and throws SerovalMalformedNodeError.

1. What is CVE-2026-116584? CVE-2026-116584 is a high-severity allocation of resources without limits or throttling vulnerability in seroval (npm), affecting versions >= 1.4.1, <= 1.6.7. It is fixed in 1.6.8. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2026-116584? CVE-2026-116584 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of seroval are affected by CVE-2026-116584? seroval (npm) versions >= 1.4.1, <= 1.6.7 is affected.
4. Is there a fix for CVE-2026-116584? Yes. CVE-2026-116584 is fixed in 1.6.8. Upgrade to this version or later.
5. Is CVE-2026-116584 exploitable, and should I be worried? Whether CVE-2026-116584 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-116584 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-116584? Upgrade seroval to 1.6.8 or later.

Other vulnerabilities in seroval