Attack Chain

1. Craft Malicious JSON: An attacker crafts a specially designed Seroval JSON payload. This payload contains values that, due to the type confusion vulnerability (CVE-2026-59940), are engineered to be misinterpreted by seroval.fromJSON() as internal Promise resolver records.
2. Deliver Payload: The attacker sends this malicious Seroval JSON input to a vulnerable server-side application that uses seroval.fromJSON() for deserialization of untrusted client input.
3. Initiate Deserialization: The vulnerable application receives the untrusted JSON and passes it to seroval.fromJSON() for processing. This typically occurs when plugins are enabled in the Seroval configuration.
4. Trigger Type Confusion: During the deserialization, seroval.fromJSON() attempts to process Promise control nodes. Due to the type confusion flaw, it fails to properly verify the type of values from the general deserialization reference table, mistakenly treating attacker-controlled data as legitimate Promise resolver records.
5. Invoke Attacker-Controlled Methods: This misinterpretation leads to the Promise control nodes operating on these attacker-controlled values, causing the unintended invocation of methods or callable wrappers that were defined through registered plugins in the downstream framework.
6. Achieve Server Compromise: Depending on the specific methods invoked and the functionality exposed by the application's plugins, this arbitrary method invocation can lead to severe consequences, including remote code execution (RCE), arbitrary file manipulation, or other forms of server compromise.

Impact

The vulnerable deserialization path can confuse attacker-created values with internal Seroval promise resolver records, leading to a deserialization side-effect primitive when untrusted JSON is processed with plugins enabled. The direct impact on applications using seroval is the ability for an attacker to influence program flow during deserialization. In downstream server frameworks, such as TanStack Start, which might register plugins returning callable wrappers, this vulnerability can be leveraged to trigger unintended server-side invocations. This can escalate to remote code execution (RCE), arbitrary file system access, or full server compromise, depending on the scope of the invoked methods. The vulnerability was privately validated against TanStack Start, confirming potential downstream exploitation.

Recommendation

• Upgrade the seroval package to version 1.5.3 or later immediately to mitigate CVE-2026-59940.
• For downstream projects accepting Seroval JSON from untrusted clients, implement defense-in-depth controls such as restricting accepted Seroval node types for client-to-server payloads.
• Restrictively allowlist plugin tags for inbound deserialization processes to prevent unintended plugin activation.
• Avoid registering plugins that produce callable or privileged values for untrusted inputs unless absolutely necessary.
• Implement regression tests to ensure deserialization cannot cause unintended server-side invocation as a side effect.