CVSS 3.1
9.3 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:NCritical (9.3). EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in @tanstack/start-server-core 1.169.39.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N@tanstack/start-server-core (npm): fixed in 1.169.39@tanstack/react-start (npm): fixed in 1.168.60@tanstack/solid-start (npm): fixed in 1.168.57@tanstack/vue-start (npm): fixed in 1.168.56Explain CVE-2026-102989 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102989?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102989?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102989 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| TanStack router | < release-2026-09-30-1747 |
| @tanstack react-start | >= 1.143.12, < 1.168.60 |
| @tanstack solid-start | >= 1.143.12, < 1.168.57 |
| @tanstack start-server-core | >= 1.143.12, < 1.169.39 |
| @tanstack vue-start | >= 1.143.12, < 1.168.56 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-qx66-fv34-fjm8 | npm | @tanstack/start-server-core | >=1.143.12 <1.169.39 | 1.169.39 |
| GHSA-qx66-fv34-fjm8 | npm | @tanstack/react-start | >=1.143.12 <1.168.60 | 1.168.60 |
| GHSA-qx66-fv34-fjm8 | npm | @tanstack/solid-start | >=1.143.12 <1.168.57 | 1.168.57 |
| GHSA-qx66-fv34-fjm8 | npm | @tanstack/vue-start | >=1.143.12 <1.168.56 | 1.168.56 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.