GHSA-9m65-766c-r333: TanStack Start - Server Core Inbound Server-function Request Deserialization Could Vulnerability

MODERATE
CWE-502 CWE-843
Published
Advisory Summary

GHSA-9m65-766c-r333 is a MODERATE inbound server-function request deserialization could vulnerability (CWE-502: Deserialization of Untrusted Data) affecting TanStack Start - Server Core libraries in the npm ecosystem. The issue involves inbound server-function request deserialization could invoke a sibling client-referenced server function. Remediation is available by upgrading affected packages to version 1.167.30.

GHSA-9m65-766c-r333 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-9m65-766c-r333
Severity MODERATE
CVSS v3.1 Base Score N/A
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product TanStack Start - Server Core
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-9m65-766c-r333

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

@tanstack/start-server-core fixed: 1.167.30
npm install @tanstack/start-server-core@1.167.30
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 @tanstack/start-server-core

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-9m65-766c-r333, inspect your project dependencies using npm:

npm ls @tanstack/start-server-core

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

Note: The npm ls @tanstack/start-server-core 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 TanStack Start - Server Core, 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 bug in seroval ≤ 1.5.2 ([upstream advisory](https://github.com/lxsmnsyc/seroval/security/advisories)) allowed a crafted JSON body sent to one TanStack Start server function to trigger invocation of a different client-referenced server function as a side effect of deserializing the request payload. This is not an authentication bypass and not remote code execution. The mechanism only invokes server functions that the same client could already reach directly via /_serverFn/<id>, and the target function's full middleware chain — including any user-supplied authentication, authorization, and inputValidator — runs as it would on a direct call. ### Impact To be exploitable in any meaningful sense, an application would need to expose a client-referenced server function that: - [ ] Performs a privileged side effect, and - [ ] Has no authentication/authorization middleware, and - [ ] Has no input validation A function meeting all three is already directly callable by any unauthenticated client at its own endpoint, so the practical impact on correctly-written applications is nil. The residual concerns are: A request to function A could cause function B to also execute, which may surprise observability/audit logging that keys off the request URL. Request-level middleware (as opposed to per-function middleware) does not re-run for the inner invocation. Server-only functions (isClientReferenced: false) cannot be reached through this mechanism. ### Patches Upgrade to @tanstack/start-server-core ≥ 1.167.30 (or the equivalent dated release of @tanstack/react-start / @tanstack/solid-start). The fix bumps seroval to ≥ 1.5.3 and adds defense-in-depth to the serialization adapter plugin shape so adapter payloads cannot be confused with internal seroval node types. ### Workarounds If you cannot upgrade immediately, ensure every createServerFn(...) exposed to the client has both an .inputValidator(...) and authentication/authorization middleware via .middleware([...]). This is recommended regardless of this advisory. ### Credits - [Mufeed VH](https://x.com/mufeedvh) of [Winfunc Research](https://winfunc.com/) - Upstream fix coordinated with Seroval maintainers https://github.com/lxsmnsyc/seroval

GHSA-9m65-766c-r333 Affected TanStack Start - Server Core Versions

1 component(s)
Fixed Versions:
1.167.30
Product / Package Ecosystem Affected Versions Fixed Version
@tanstack/start-server-core
npm
< 1.167.30
1.167.30

References

Frequently Asked Questions

What is GHSA-9m65-766c-r333?
GHSA-9m65-766c-r333 is a security vulnerability in TanStack Start - Server Core involving Inbound server-function request deserialization could invoke a sibling client-referenced server function under CWE-502: Deserialization of Untrusted Data.
Which TanStack Start - Server Core versions are affected?
Affected versions include releases prior to 1.167.30 across affected packages: @tanstack/start-server-core.
What version fixes GHSA-9m65-766c-r333?
Upgrading to 1.167.30 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @tanstack/start-server-core affected?
Yes, @tanstack/start-server-core is affected in releases prior to 1.167.30. Upgrade your dependency to 1.167.30 or later.
What CWE is associated with GHSA-9m65-766c-r333?
GHSA-9m65-766c-r333 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 GHSA-9m65-766c-r333?
Run the dependency tree command: 'npm ls @tanstack/start-server-core'. 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-9m65-766c-r333",
  "modified" : "2026-05-14T16:37:10Z",
  "published" : "2026-05-14T16:37:10Z",
  "aliases" : [ ],
  "summary" : "TanStack Start - Server Core: Inbound server-function request deserialization could invoke a sibling client-referenced server function",
  "details" : "### Summary\nA type-confusion bug in seroval ≤ 1.5.2 ([upstream advisory](https://github.com/lxsmnsyc/seroval/security/advisories)) allowed a crafted JSON body sent to one TanStack Start server function to trigger invocation of a different client-referenced server function as a side effect of deserializing the request payload.\n\nThis is not an authentication bypass and not remote code execution. The mechanism only invokes server functions that the same client could already reach directly via /_serverFn/<id>, and the target function's full middleware chain — including any user-supplied authentication, authorization, and inputValidator — runs as it would on a direct call.\n\n### Impact\nTo be exploitable in any meaningful sense, an application would need to expose a client-referenced server function that:\n\n- [ ] Performs a privileged side effect, and\n- [ ] Has no authentication/authorization middleware, and\n- [ ] Has no input validation\n\nA function meeting all three is already directly callable by any unauthenticated client at its own endpoint, so the practical impact on correctly-written applications is nil. The residual concerns are:\n\nA request to function A could cause function B to also execute, which may surprise observability/audit logging that keys off the request URL.\n\nRequest-level middleware (as opposed to per-function middleware) does not re-run for the inner invocation.\nServer-only functions (isClientReferenced: false) cannot be reached through this mechanism.\n\n### Patches\nUpgrade to @tanstack/start-server-core ≥ 1.167.30 (or the equivalent dated release of @tanstack/react-start / @tanstack/solid-start). The fix bumps seroval to ≥ 1.5.3 and adds defense-in-depth to the serialization adapter plugin shape so adapter payloads cannot be confused with internal seroval node types.\n\n### Workarounds\nIf you cannot upgrade immediately, ensure every createServerFn(...) exposed to the client has both an .inputValidator(...) and authentication/authorization middleware via .middleware([...]). This is recommended regardless of this advisory.\n\n### Credits\n- [Mufeed VH](https://x.com/mufeedvh) of [Winfunc Research](https://winfunc.com/)\n- Upstream fix coordinated with Seroval maintainers https://github.com/lxsmnsyc/seroval",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@tanstack/start-server-core"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.167.30"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/TanStack/router/security/advisories/GHSA-9m65-766c-r333"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/TanStack/router"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/lxsmnsyc/seroval/security/advisories"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502", "CWE-843" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-14T16:37:10Z",
    "nvd_published_at" : null
  }
}