Vulnerability Overview: What Is CVE-2026-102989 @tanstack/start-server-core?
Specifically, CVE-2026-102989 @tanstack/start-server-core is a critical reflected cross‑site scripting (XSS) flaw in TanStack Start server‑function responses. The OSV advisory GHSA-qx66-fv34-fjm8 explains that an unauthenticated attacker can craft a malicious URL which, when opened, returns attacker‑controlled HTML from the same origin, enabling script execution with the victim’s credentials.
| Vulnerability Attribute | Documented Detail | Security Implication |
|---|---|---|
| OSV Advisory ID | GHSA-qx66-fv34-fjm8 | Reference for all advisory data |
| CVE Alias | CVE-2026-102989 | Standard NVD identifier |
| Affected Package (primary) | @tanstack/start-server-core | Entry point for server‑function transport |
| Ecosystem | npm | JavaScript package manager |
| Severity | CRITICAL | Potential for full account compromise |
| CVSS Score (v3) | Not specified in source advisory | Score unavailable; vector provided below |
| CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N | Network‑accessible, low complexity, high impact on confidentiality and integrity |
| CWE IDs | CWE-79 | Improper neutralization of input during web page generation (XSS) |
| Published Date | 2026-10-15 | Public disclosure date |
| Modified Date | 2026-10-15 | Last advisory update |
| Fixed Version (primary) | @tanstack/start-server-core@1.169.39 | Version containing the remediation |
In-Depth Technical Analysis & Root Cause of CVE-2026-102989 @tanstack/start-server-core
Consequently, the vulnerability stems from the server‑function transport layer accepting arbitrary request payload fields and merging them into internal middleware state without proper sanitization. Specifically, malformed payloads can place attacker‑controlled data into the error path, which the response handler later treats as a legitimate HTTP response object. As a result, the server returns attacker‑crafted HTML that executes in the victim’s browser under the same origin.
Affected Packages & Versions: Is Your @tanstack/start-server-core Deployment Vulnerable?
In addition, four TanStack Start packages are impacted. The vulnerable range starts at version 1.143.12 and ends before the respective patched releases.
| Package Name | Ecosystem | Vulnerable Version Range | Fixed Version / Boundary | Status |
|---|---|---|---|---|
| @tanstack/start-server-core | npm | >=1.143.12 <1.169.39 | 1.169.39 | Patched |
| @tanstack/react-start | npm | >=1.143.12 <1.168.60 | 1.168.60 | Patched |
| @tanstack/solid-start | npm | >=1.143.12 <1.168.57 | 1.168.57 | Patched |
| @tanstack/vue-start | npm | >=1.143.12 <1.168.56 | 1.168.56 | Patched |
Severity, Risk & CVSS Score Assessment for CVE-2026-102989 @tanstack/start-server-core
Specifically, the CVSS vector indicates a network‑reachable attack (AV:N) with low attack complexity (AC:L) and no authentication required (PR:N). The impact on confidentiality and integrity is high (C:H/I:H) while availability is unchanged (A:N). Consequently, the overall risk is critical, especially for applications exposing server‑function endpoints to the public internet.
Who Should Investigate? Workload & Application Triage
Therefore, development teams that ship TanStack Start applications, DevOps engineers maintaining CI/CD pipelines, and application‑security analysts should prioritize triage. Specifically, audit any Docker images, server‑less functions, or static site generators that include the affected packages. Moreover, verify lockfiles (package‑lock.json, yarn.lock) for the vulnerable ranges.
Detection: How to Check @tanstack/start-server-core in SBOM & Dependencies
First, run ecosystem‑specific commands to list installed versions:
npm ls @tanstack/start-server-corenpm audit --json | jq '.advisories | select(.id=="GHSA-qx66-fv34-fjm8")'- For SBOMs, use CycloneDX:
cyclonedx-bom -i . -o sbom.xml && grep "@tanstack/start-server-core" sbom.xml - For SPDX:
spdx-sbom-generator -p . -o sbom.spdx && grep "@tanstack/start-server-core" sbom.spdx
How to Fix CVE-2026-102989 @tanstack/start-server-core: Patch, Upgrade & Remediation Guide
Consequently, remediation consists of upgrading each affected package to its patched version or later. Follow these steps:
- Update the package in
package.json:npm install @tanstack/start-server-core@^1.169.39 @tanstack/react-start@^1.168.60 @tanstack/solid-start@^1.168.57 @tanstack/vue-start@^1.168.56 --save-exact
- Run
npm installto refresh the lockfile. - Execute the test suite to ensure no regressions.
- Rebuild container images or server‑less bundles.
- Redeploy to production environments.
If an immediate upgrade is not possible, apply temporary mitigations such as edge‑WAF rules that block requests lacking the x-tsr-serverFn: true header or enforce a restrictive Content‑Security‑Policy on server‑function responses.
Post-Remediation Verification & Audit Checklist
- Confirm the upgraded version appears in
npm lsoutput. - Regenerate the SBOM and verify the vulnerable range is absent.
- Run
npm auditagain to ensure no remaining findings for GHSA‑qx66‑fv34‑fjm8. - Document the remediation in the change‑log and ticketing system.
Frequently Asked Questions (FAQ) About CVE-2026-102989 @tanstack/start-server-core
What is the severity and CVSS score of CVE-2026-102989 @tanstack/start-server-core?
The advisory classifies the issue as CRITICAL. The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N, indicating a high impact on confidentiality and integrity.
Which versions of @tanstack/start-server-core are vulnerable?
All versions from 1.143.12 up to, but not including, 1.169.39 are vulnerable.
Is there an official patch or fixed version for CVE-2026-102989 @tanstack/start-server-core?
Yes. The fixed version is @tanstack/start-server-core@1.169.39. Corresponding patches exist for the other TanStack Start packages.
Can CVE-2026-102989 be exploited remotely?
Yes. An unauthenticated attacker can craft a malicious URL that, when visited, triggers the reflected XSS without any prior authentication.
How do I check if my project uses the affected @tanstack/start-server-core version?
Run npm ls @tanstack/start-server-core or inspect your lockfile for a version in the vulnerable range.
What is the recommended upgrade path?
Upgrade directly to version 1.169.39 or any later release. Ensure all related TanStack Start packages are also updated to their respective patched versions.
DevSecOps & Supply Chain Defense Checklist for CVE-2026-102989 @tanstack/start-server-core
- Pin dependencies to exact versions in lockfiles.
- Integrate automated vulnerability scanning (e.g.,
npm audit, Snyk) into CI pipelines. - Generate and monitor SBOMs for every build artifact.
- Establish a vulnerability SLA (e.g., remediate critical findings within 48 hours).
- Apply edge‑WAF rules for server‑function endpoints as a defense‑in‑depth measure.
Explore CVE-2026-102989 @tanstack/start-server-core on cve.sbom.guru
For full advisory details, visit the GHSA-qx66-fv34-fjm8 advisory page. You can also view the CVE entry at CVE-2026-102989 and explore related PURLs such as @tanstack/start-server-core.
Authoritative References
- GitHub Security Advisory GHSA-qx66-fv34-fjm8
- NVD CVE-2026-102989 Details
- Fix Pull Request #8573
- Commit Introducing the Fix
Key Takeaways for CVE-2026-102989 @tanstack/start-server-core
- Identifier: CVE-2026-102989 / GHSA-qx66-fv34-fjm8
- Vulnerability: Reflected XSS in TanStack Start server‑function responses
- Affected range: >=1.143.12 <1.169.39 (primary package)
- Fixed version: @tanstack/start-server-core@1.169.39 (and related packages)
- Immediate action: Upgrade, verify lockfiles, and regenerate SBOMs
Advisory Freshness Note
Vulnerability intelligence evolves rapidly. Regularly review the advisory page on cve.sbom.guru for updates, new patches, or additional mitigation guidance.