CVE-2026-59940: seroval `seroval.fromJSON()` Promise Resolver Type Confusion Vulnerability

CRITICAL
Advisory Identifier: GHSA-mv8w-475r-vwqw
CVSS 9.8
CWE-502 CWE-843
Published
Advisory Summary

CVE-2026-59940 is a CRITICAL (CVSS 9.8) `seroval.fromjson()` promise resolver type confusion vulnerability (CWE-502: Deserialization of Untrusted Data) affecting seroval libraries in the npm ecosystem. The issue involves `seroval.fromjson()` promise resolver type confusion invokes attacker-controlled methods during deserialization. Remediation is available by upgrading affected packages to version 1.5.3.

CVE-2026-59940 at a Glance

CVE Identifier CVE-2026-59940
GHSA Identifier GHSA-mv8w-475r-vwqw
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product seroval
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-59940

To remediate this vulnerability, upgrade all affected seroval dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

seroval fixed: 1.5.3
npm install seroval@1.5.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls seroval

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-59940, inspect your project dependencies using npm:

npm ls seroval

Analyze the terminal output to locate any version of seroval in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.5.3), your application is affected.

Note: The npm ls seroval command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In seroval, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A type confusion issue in `seroval.fromJSON()` allowed attacker-controlled JSON input to cause Promise control nodes to operate on values from the general deserialization reference table without first verifying that those values were genuine internal promise resolver records. In applications that deserialize untrusted Seroval JSON with plugins enabled, this could allow attacker-controlled deserialization side effects. In downstream server frameworks that register plugins returning callable wrappers, this primitive could become unintended server-side invocation and, depending on exposed application functionality, remote code execution or equivalent server compromise. The issue was fixed in `seroval@1.5.3`. ## Affected package - Package: `seroval` - Affected API: `fromJSON()` - Affected versions: versions prior to `1.5.3` that contain the vulnerable Promise resolver reference handling - Patched version: `1.5.3` ## Impact The vulnerable deserialization path could confuse attacker-created values in the general reference table with Seroval's internal promise resolver records. Direct impact in `seroval` is a deserialization side-effect primitive when untrusted JSON is deserialized with plugins enabled. Downstream impact depends on registered plugins and framework usage. If a downstream framework registers plugins that deserialize sensitive callable wrappers, attacker-controlled input may be able to trigger unintended server-side invocation during deserialization. A concrete downstream impact scenario was validated privately against TanStack Start before the `1.5.3` fix. With `seroval@1.5.3`, the downstream reproducer no longer succeeds. ## Remediation Upgrade to `seroval@1.5.3` or later. Downstream projects that accept Seroval JSON from untrusted clients should also consider defense-in-depth controls: - restrict accepted Seroval node types for client-to-server payloads; - allowlist plugin tags for inbound deserialization; - avoid registering plugins that produce callable or privileged values for untrusted inputs unless strictly necessary; - add regression tests ensuring deserialization cannot cause unintended server-side invocation as a side effect. ## Fix verification The original private reproducer was verified against `seroval@1.5.2` and no longer reproduces against `seroval@1.5.3`. Validation results: - `seroval@1.5.2`: vulnerable behavior reproduced. - `seroval@1.5.3`: deserialization aborts before the attacker-controlled side effect occurs. - TanStack Start downstream proof with `seroval@1.5.3`: no evidence side effect is produced. ## Credit Reported by [Mufeed VH](https://x.com/mufeedvh) from [Winfunc Research](https://winfunc.com). ## Disclosure / coordination note The downstream TanStack Start impact was coordinated privately. Technical exploit details and proof-of-concept reproduction material have been omitted from this advisory draft for discretion.

CVE-2026-59940 Affected seroval Versions

1 component(s)
Fixed Versions:
1.5.3
Product / Package Ecosystem Affected Versions Fixed Version
seroval
npm
< 1.5.3
1.5.3

References

Frequently Asked Questions

What is CVE-2026-59940?
CVE-2026-59940 is a security vulnerability in seroval involving `seroval.fromJSON()` Promise resolver type confusion invokes attacker-controlled methods during deserialization under CWE-502: Deserialization of Untrusted Data.
Which seroval versions are affected?
Affected versions include releases prior to 1.5.3 across affected packages: seroval.
What version fixes CVE-2026-59940?
Upgrading to 1.5.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is seroval affected?
Yes, seroval is affected in releases prior to 1.5.3. Upgrade your dependency to 1.5.3 or later.
What is the CVSS score of CVE-2026-59940?
CVE-2026-59940 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-59940?
CVE-2026-59940 is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check npm dependencies for CVE-2026-59940?
Run the dependency tree command: 'npm ls seroval'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-mv8w-475r-vwqw",
  "modified" : "2026-07-24T16:14:06Z",
  "published" : "2026-07-24T16:14:05Z",
  "aliases" : [ "CVE-2026-59940" ],
  "summary" : "seroval: `seroval.fromJSON()` Promise resolver type confusion invokes attacker-controlled methods during deserialization",
  "details" : "## Summary\n\nA type confusion issue in `seroval.fromJSON()` allowed attacker-controlled JSON input to cause Promise control nodes to operate on values from the general deserialization reference table without first verifying that those values were genuine internal promise resolver records.\n\nIn applications that deserialize untrusted Seroval JSON with plugins enabled, this could allow attacker-controlled deserialization side effects. In downstream server frameworks that register plugins returning callable wrappers, this primitive could become unintended server-side invocation and, depending on exposed application functionality, remote code execution or equivalent server compromise.\n\nThe issue was fixed in `seroval@1.5.3`.\n\n## Affected package\n\n- Package: `seroval`\n- Affected API: `fromJSON()`\n- Affected versions: versions prior to `1.5.3` that contain the vulnerable Promise resolver reference handling\n- Patched version: `1.5.3`\n\n## Impact\n\nThe vulnerable deserialization path could confuse attacker-created values in the general reference table with Seroval's internal promise resolver records.\n\nDirect impact in `seroval` is a deserialization side-effect primitive when untrusted JSON is deserialized with plugins enabled. Downstream impact depends on registered plugins and framework usage. If a downstream framework registers plugins that deserialize sensitive callable wrappers, attacker-controlled input may be able to trigger unintended server-side invocation during deserialization.\n\nA concrete downstream impact scenario was validated privately against TanStack Start before the `1.5.3` fix. With `seroval@1.5.3`, the downstream reproducer no longer succeeds.\n\n## Remediation\n\nUpgrade to `seroval@1.5.3` or later.\n\nDownstream projects that accept Seroval JSON from untrusted clients should also consider defense-in-depth controls:\n\n- restrict accepted Seroval node types for client-to-server payloads;\n- allowlist plugin tags for inbound deserialization;\n- avoid registering plugins that produce callable or privileged values for untrusted inputs unless strictly necessary;\n- add regression tests ensuring deserialization cannot cause unintended server-side invocation as a side effect.\n\n## Fix verification\n\nThe original private reproducer was verified against `seroval@1.5.2` and no longer reproduces against `seroval@1.5.3`.\n\nValidation results:\n\n- `seroval@1.5.2`: vulnerable behavior reproduced.\n- `seroval@1.5.3`: deserialization aborts before the attacker-controlled side effect occurs.\n- TanStack Start downstream proof with `seroval@1.5.3`: no evidence side effect is produced.\n\n## Credit\n\nReported by [Mufeed VH](https://x.com/mufeedvh) from [Winfunc Research](https://winfunc.com).\n\n## Disclosure / coordination note\n\nThe downstream TanStack Start impact was coordinated privately. Technical exploit details and proof-of-concept reproduction material have been omitted from this advisory draft for discretion.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "seroval"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.5.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.5.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/lxsmnsyc/seroval/security/advisories/GHSA-mv8w-475r-vwqw"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/lxsmnsyc/seroval"
  }, {
    "type" : "WEB",
    "url" : "https://www.npmjs.com/package/seroval/v/1.5.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502", "CWE-843" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-07-24T16:14:05Z",
    "nvd_published_at" : null
  }
}