CVE-2026-45321: TanStack Unspecified Vulnerability
Reference page built from the source records below, each shown as its source publishes it. Dataset version ref-b9296ea043f3, updated 2026-11-02T23:39:54.475Z.
CISA Known Exploited Vulnerabilities
- Name
- TanStack Unspecified Vulnerability
- Vendor
- TanStack
- Product
- TanStack
- Added to the catalog
- 2026-05-27
- Due date for US federal agencies
- 2026-06-10
- Catalog version
- 2026.10.30
TanStack contains an unspecified vulnerability that allowed malicious versions of the product to be published to the npm registry to publish credential-stealing malware under a trusted identity.
Required action (CISA)
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Ransomware use: CISA marks this vulnerability as known to be used in ransomware campaigns. CISA does not say which group used it.
Links in CISA's notes
- https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx
- https://nvd.nist.gov/vuln/detail/CVE-2026-45321
Read on 2026-11-02T23:39:54.475Z under licence cisa-kev-cc0@b0067899 from https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
NVD analysis
- Status
- Analyzed
- Published
- 2026-05-12T01:16:46.820
- Last modified
- 2026-10-26T18:10:00.173
- Weaknesses
- CWE-506
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for TanStack/router, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a pull_request_target "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity. Each affected package received exactly two malicious versions, published a few minutes apart.
| Metric | Score | Severity | Vector | Scored by |
|---|---|---|---|---|
| CVSS 3.1 | 9.6 | CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H | [email protected] (Secondary) |
References
- https://github.com/TanStack/router/issues/7383 (Issue Tracking)
- https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx (Mitigation, Vendor Advisory)
- https://tanstack.com/blog/npm-supply-chain-compromise-postmortem (Exploit, Vendor Advisory)
- https://www.stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem (Exploit, Third Party Advisory)
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-45321 (US Government Resource)
This product uses the NVD API but is not endorsed or certified by the NVD.
Read on 2026-11-02T23:42:31.494Z under licence nvd-api-terms-of-use@ff2a5288 from https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-45321
CVE record
- Title (CNA)
- Malware in 42 @tanstack/* packages exfiltrates cloud credentials, GitHub tokens, and SSH keys
- Assigner
- GitHub_M
- State
- PUBLISHED
- Published
- 2026-05-12T00:12:35.452Z
- Updated
- 2026-08-04T03:56:09.005Z
- Problem types
- CWE-506: Embedded Malicious Code
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for TanStack/router, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a pull_request_target "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity. Each affected package received exactly two malicious versions, published a few minutes apart.
References
- https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx
- https://github.com/TanStack/router/issues/7383
- https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
- https://www.stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem
Read on 2026-11-03T02:20:10.437Z under licence cve-terms-of-use@81bfa2f3 from https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/45xxx/CVE-2026-45321.json
GitHub Advisory Database
GHSA-g7cv-rxg3-hmpx: Malware in @tanstack/* packages exfiltrates cloud credentials, GitHub tokens, and SSH keys
- Severity (GitHub)
- critical
- CVSS
- 9.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
- Weaknesses
- CWE-506
- Published
- 2026-05-12T00:12:49Z
- Updated
- 2026-06-08T23:53:12Z
- npm @tanstack/arktype-adapter: affected = 1.166.12, first patched 1.166.16
- npm @tanstack/eslint-plugin-router: affected = 1.161.9, first patched 1.161.13
- npm @tanstack/eslint-plugin-start: affected = 0.0.4, first patched 0.0.8
- npm @tanstack/history: affected = 1.161.9, first patched 1.161.13
- npm @tanstack/nitro-v2-vite-plugin: affected = 1.154.12, first patched 1.154.16
- npm @tanstack/react-router: affected = 1.169.5, first patched 1.169.9
- npm @tanstack/react-router-devtools: affected = 1.166.16, first patched 1.166.20
- npm @tanstack/react-router-ssr-query: affected = 1.166.15, first patched 1.166.19
- npm @tanstack/react-start: affected = 1.167.68, first patched 1.167.72
- npm @tanstack/react-start-client: affected = 1.166.51, first patched 1.166.55
- npm @tanstack/react-start-rsc: affected = 0.0.47, first patched 0.0.51
- npm @tanstack/react-start-server: affected = 1.166.55, first patched 1.166.59
- npm @tanstack/router-cli: affected = 1.166.46, first patched 1.166.50
- npm @tanstack/router-core: affected = 1.169.5, first patched 1.169.9
- npm @tanstack/router-devtools: affected = 1.166.16, first patched 1.166.20
- npm @tanstack/router-devtools-core: affected = 1.167.6, first patched 1.167.10
- npm @tanstack/router-generator: affected = 1.166.45, first patched 1.166.49
- npm @tanstack/router-plugin: affected = 1.167.38, first patched 1.167.42
- npm @tanstack/router-ssr-query-core: affected = 1.168.3, first patched 1.168.7
- npm @tanstack/router-utils: affected = 1.161.11, first patched 1.161.15
- npm @tanstack/router-vite-plugin: affected = 1.166.53, first patched 1.166.57
- npm @tanstack/solid-router: affected = 1.169.5, first patched 1.169.9
- npm @tanstack/solid-router-devtools: affected = 1.166.16, first patched 1.166.20
- npm @tanstack/solid-router-ssr-query: affected = 1.166.15, first patched 1.166.19
- npm @tanstack/solid-start: affected = 1.167.65, first patched 1.167.69
- npm @tanstack/solid-start-client: affected = 1.166.50, first patched 1.166.54
- npm @tanstack/solid-start-server: affected = 1.166.54, first patched 1.166.58
- npm @tanstack/start-client-core: affected = 1.168.5, first patched 1.168.9
- npm @tanstack/start-fn-stubs: affected = 1.161.9, first patched 1.161.13
- npm @tanstack/start-plugin-core: affected = 1.169.23, first patched 1.169.27
- npm @tanstack/start-server-core: affected = 1.167.33, first patched 1.167.37
- npm @tanstack/start-static-server-functions: affected = 1.166.44, first patched 1.166.48
- npm @tanstack/start-storage-context: affected = 1.166.38, first patched 1.166.42
- npm @tanstack/valibot-adapter: affected = 1.166.12, first patched 1.166.16
- npm @tanstack/virtual-file-routes: affected = 1.161.10, first patched 1.161.14
- npm @tanstack/vue-router: affected = 1.169.5, first patched 1.169.9
- npm @tanstack/vue-router-devtools: affected = 1.166.16, first patched 1.166.20
- npm @tanstack/vue-router-ssr-query: affected = 1.166.15, first patched 1.166.19
- npm @tanstack/vue-start: affected = 1.167.61, first patched 1.167.65
- npm @tanstack/vue-start-client: affected = 1.166.46, first patched 1.166.50
- npm @tanstack/vue-start-server: affected = 1.166.50, first patched 1.166.54
- npm @tanstack/zod-adapter: affected = 1.166.12, first patched 1.166.16
- npm @tanstack/arktype-adapter: affected = 1.166.15, first patched 1.166.16
- npm @tanstack/eslint-plugin-router: affected = 1.161.12, first patched 1.161.13
- npm @tanstack/eslint-plugin-start: affected = 0.0.7, first patched 0.0.8
- npm @tanstack/history: affected = 1.161.12, first patched 1.161.13
- npm @tanstack/nitro-v2-vite-plugin: affected = 1.154.15, first patched 1.154.16
- npm @tanstack/react-router: affected = 1.169.8, first patched 1.169.9
- npm @tanstack/react-router-devtools: affected = 1.166.19, first patched 1.166.20
- npm @tanstack/react-router-ssr-query: affected = 1.166.18, first patched 1.166.19
- npm @tanstack/react-start: affected = 1.167.71, first patched 1.167.72
- npm @tanstack/react-start-client: affected = 1.166.54, first patched 1.166.55
- npm @tanstack/react-start-rsc: affected = 0.0.50, first patched 0.0.51
- npm @tanstack/react-start-server: affected = 1.166.58, first patched 1.166.59
- npm @tanstack/router-cli: affected = 1.166.49, first patched 1.166.50
- npm @tanstack/router-core: affected = 1.169.8, first patched 1.169.9
- npm @tanstack/router-devtools: affected = 1.166.19, first patched 1.166.20
- npm @tanstack/router-devtools-core: affected = 1.167.9, first patched 1.167.10
- npm @tanstack/router-generator: affected = 1.166.48, first patched 1.166.49
- npm @tanstack/router-plugin: affected = 1.167.41, first patched 1.167.42
- npm @tanstack/router-ssr-query-core: affected = 1.168.6, first patched 1.168.7
- npm @tanstack/router-utils: affected = 1.161.14, first patched 1.161.15
- npm @tanstack/router-vite-plugin: affected = 1.166.56, first patched 1.166.57
- npm @tanstack/solid-router: affected = 1.169.8, first patched 1.169.9
- npm @tanstack/solid-router-devtools: affected = 1.166.19, first patched 1.166.20
- npm @tanstack/solid-router-ssr-query: affected = 1.166.18, first patched 1.166.19
- npm @tanstack/solid-start: affected = 1.167.68, first patched 1.167.69
- npm @tanstack/solid-start-client: affected = 1.166.53, first patched 1.166.54
- npm @tanstack/solid-start-server: affected = 1.166.57, first patched 1.166.58
- npm @tanstack/start-client-core: affected = 1.168.8, first patched 1.168.9
- npm @tanstack/start-fn-stubs: affected = 1.161.12, first patched 1.161.13
- npm @tanstack/start-plugin-core: affected = 1.169.26, first patched 1.169.27
- npm @tanstack/start-server-core: affected = 1.167.36, first patched 1.167.37
- npm @tanstack/start-static-server-functions: affected = 1.166.47, first patched 1.166.48
- npm @tanstack/start-storage-context: affected = 1.166.41, first patched 1.166.42
- npm @tanstack/valibot-adapter: affected = 1.166.15, first patched 1.166.16
- npm @tanstack/virtual-file-routes: affected = 1.161.13, first patched 1.161.14
- npm @tanstack/vue-router: affected = 1.169.8, first patched 1.169.9
- npm @tanstack/vue-router-devtools: affected = 1.166.19, first patched 1.166.20
- npm @tanstack/vue-router-ssr-query: affected = 1.166.18, first patched 1.166.19
- npm @tanstack/vue-start: affected = 1.167.64, first patched 1.167.65
- npm @tanstack/vue-start-client: affected = 1.166.49, first patched 1.166.50
- npm @tanstack/vue-start-server: affected = 1.166.53, first patched 1.166.54
- npm @tanstack/zod-adapter: affected = 1.166.15, first patched 1.166.16
## Summary
On 2026-05-11, between approximately 19:20 and 19:26 UTC, 84 malicious versions across 42 `@tanstack/*` packages were published to the npm registry. The publishes were authenticated via the legitimate GitHub Actions OIDC trusted-publisher binding for `TanStack/router`, but the publish workflow itself was not modified. The attacker chained three known vulnerability classes — a `pull_request_target` "Pwn Request" misconfiguration, GitHub Actions cache poisoning across the fork↔base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — to publish credential-stealing malware under a trusted identity.
Each affected package received exactly two malicious versions, published a few minutes apart.
## Impact
A user installing any affected version executes a payload (~2.3 MB obfuscated `router_init.js`) at install time that:
- Harvests credentials from common locations:
- AWS instance metadata (IMDS) and Secrets Manager
- GCP metadata service
- Kubernetes service-account tokens
- HashiCorp Vault tokens
- `~/.npmrc` (npm tokens)
- GitHub tokens (env vars, `gh` CLI config, `.git-credentials`)
- SSH private keys (`~/.ssh/`)
- Exfiltrates harvested data over the Session/Oxen messenger file-upload network (`filev2.getsession.org`, `seed{1,2,3}.getsession.org`). This is end-to-end encrypted with no attacker-controlled C2, so blocking by IP or domain is the only network mitigation.
- Enumerates packages that the victim maintains via `registry.npmjs.org/-/v1/search?text=maintainer:<user>` and republishes them with the same injection, propagating the compromise across npm.
Any developer or CI environment that ran `npm install`, `pnpm install`, or `yarn install` against an affected version on 2026-05-11 should be considered compromised. All credentials accessible to the install process should be rotated immediately. Cloud audit logs should be reviewed for activity originating from the affected hosts during and after the install window.
## Detection
Inspect the published manifest of any pinned `@tanstack/*` version. Malicious manifests contain this exact `optionalDependencies` entry:
```json
"optionalDependencies": {
"@tanstack/setup": "github:tanstack/router#79ac49eedf774dd4b0cfa308722bc463cfe5885c"
}
```
To check a version without running install scripts:
```bash
npm pack @tanstack/<name>@<version> # downloads tarball; does NOT execute lifecycle scripts
tar -xzf *.tgz
grep -A3 optionalDependencies package/package.json
ls -la package/router_init.js # malicious payload, ~2.3 MB, present at package root
```
The payload file `router_init.js` is approximately 2.3 MB of obfuscated JavaScript. It is placed at the tarball root and is intentionally not declared in the package's `"files"` array, so it does not appear in the package's documented contents.
## Mechanism
`@tanstack/setup` is not a real package on the npm registry. The `github:tanstack/router#79ac49ee...` specifier resolves to an orphan commit pushed to a fork in the `tanstack/router` GitHub fork network. GitHub serves commits across the entire fork network for git-URL dependencies, so the attacker did not require write access to `TanStack/router` itself — only the ability to fork and push to their own fork.
When npm processes the optional dependency, it:
1. Fetches the orphan commit from the fork network.
2. Installs the commit's declared dependencies (which include a real `bun` binary).
3. Runs the commit's `prepare` lifecycle script: `bun run tanstack_runner.js && exit 1`. The trailing `exit 1` causes the optional install to fail, after which npm silently discards it — leaving no `node_modules` trace.
4. The `tanstack_runner.js` script in turn executes `router_init.js` from the host package's tarball.
## Patches
Affected versions are being deprecated on npm with a `SECURITY:` notice. Where npm policy allows (no existing third-party dependents), affected versions are also being unpublished. The npm security team has been engaged to pull tarballs server-side for versions that cannot be unpublished.
Clean follow-up releases are being prepared. Update to the patched version listed in the affected-products table for each package, then reinstall from a clean lockfile.
## Workarounds
Until clean follow-up releases are available:
- Pin every `@tanstack/*` dependency to a known-good version published before 2026-05-11 19:00 UTC. The last known-good version for most affected packages was published on 2026-03-15.
- Delete `node_modules` and the lockfile, then reinstall to ensure no transitive dependency resolves to a malicious version.
- Configure npm to skip lifecycle scripts on install (`npm config set ignore-scripts true`) as a temporary defense-in-depth measure.
- For CI, audit any pipeline that ran `install` against `@tanstack/*` between 19:20 and 19:30 UTC on 2026-05-11. Treat the runner as compromised and rotate any secrets it had access to.
## Indicators of compromise
| Indicator | Value |
|---|---|
| Malicious git ref | `github:tanstack/router#79ac49eedf774dd4b0cfa308722bc463cfe5885c` |
| Fictitious package name | `@tanstack/setup` |
| Payload filename | `router_init.js` (~2.3 MB, package root, undeclared in `files`) |
| Helper filename in orphan commit | `tanstack_runner.js` |
| Exfiltration network | `filev2.getsession.org`, `seed1.getsession.org`, `seed2.getsession.org`, `seed3.getsession.org` |
| Second-stage payload URLs | `https://litter.catbox.moe/h8nc9u.js`, `https://litter.catbox.moe/7rrc6l.mjs` |
| Poisoned cache key | `Linux-pnpm-store-6f9233a50def742c09fde54f56553d6b449a535adf87d4083690539f49ae4da11` |
| Publish window (UTC) | 2026-05-11 19:20 — 19:26 |
| Publish mechanism | GitHub Actions OIDC trusted publisher (`oidc:db7d6f54-05d5-412b-8a10-e7a8398b303e`) |
| Workflow runs | https://github.com/TanStack/router/actions/runs/25613093674 (attempt 4), https://github.com/TanStack/router/actions/runs/25691781302 |
| Attacker GitHub accounts | `zblgg` (id 127806521), `voicproducoes` (id 269549300) |
| Attacker fork (renamed to evade detection) | https://github.com/zblgg/configuration |
## Credits
- The security researcher who initially disclosed the vulnerability publicly with detailed analysis at https://github.com/TanStack/router/issues/7383
## References
- Public incident tracking issue: https://github.com/TanStack/router/issues/7383
- Related research:
- Adnan Khan, "The Monsters in Your Build Cache: GitHub Actions Cache Poisoning" (May 2024)
- GitHub Security Lab, "Keeping your GitHub Actions and workflows secure: Preventing Pwn Requests"
- StepSecurity, "tj-actions/changed-files action is compromised" (March 2025) — the malicious payload reuses this incident's runner-memory extraction technique verbatim
Read on 2026-11-03T00:48:03.703Z under licence ghsa-cc-by-4.0@9e5f1b3c from https://api.github.com/advisories/GHSA-g7cv-rxg3-hmpx
Also known as / affected packages
GHSA-g7cv-rxg3-hmpx
Also known as: CVE-2026-45321. OSV.dev record, GitHub advisory.
- npm @tanstack/arktype-adapter: introduced 1.166.12, fixed 1.166.16
- npm @tanstack/eslint-plugin-router: introduced 1.161.9, fixed 1.161.13
- npm @tanstack/eslint-plugin-start: introduced 0.0.4, fixed 0.0.8
- npm @tanstack/history: introduced 1.161.9, fixed 1.161.13
- npm @tanstack/nitro-v2-vite-plugin: introduced 1.154.12, fixed 1.154.16
- npm @tanstack/react-router: introduced 1.169.5, fixed 1.169.9
- npm @tanstack/react-router-devtools: introduced 1.166.16, fixed 1.166.20
- npm @tanstack/react-router-ssr-query: introduced 1.166.15, fixed 1.166.19
- npm @tanstack/react-start: introduced 1.167.68, fixed 1.167.72
- npm @tanstack/react-start-client: introduced 1.166.51, fixed 1.166.55
- npm @tanstack/react-start-rsc: introduced 0.0.47, fixed 0.0.51
- npm @tanstack/react-start-server: introduced 1.166.55, fixed 1.166.59
- npm @tanstack/router-cli: introduced 1.166.46, fixed 1.166.50
- npm @tanstack/router-core: introduced 1.169.5, fixed 1.169.9
- npm @tanstack/router-devtools: introduced 1.166.16, fixed 1.166.20
- npm @tanstack/router-devtools-core: introduced 1.167.6, fixed 1.167.10
- npm @tanstack/router-generator: introduced 1.166.45, fixed 1.166.49
- npm @tanstack/router-plugin: introduced 1.167.38, fixed 1.167.42
- npm @tanstack/router-ssr-query-core: introduced 1.168.3, fixed 1.168.7
- npm @tanstack/router-utils: introduced 1.161.11, fixed 1.161.15
- npm @tanstack/router-vite-plugin: introduced 1.166.53, fixed 1.166.57
- npm @tanstack/solid-router: introduced 1.169.5, fixed 1.169.9
- npm @tanstack/solid-router-devtools: introduced 1.166.16, fixed 1.166.20
- npm @tanstack/solid-router-ssr-query: introduced 1.166.15, fixed 1.166.19
- npm @tanstack/solid-start: introduced 1.167.65, fixed 1.167.69
- npm @tanstack/solid-start-client: introduced 1.166.50, fixed 1.166.54
- npm @tanstack/solid-start-server: introduced 1.166.54, fixed 1.166.58
- npm @tanstack/start-client-core: introduced 1.168.5, fixed 1.168.9
- npm @tanstack/start-fn-stubs: introduced 1.161.9, fixed 1.161.13
- npm @tanstack/start-plugin-core: introduced 1.169.23, fixed 1.169.27
- npm @tanstack/start-server-core: introduced 1.167.33, fixed 1.167.37
- npm @tanstack/start-static-server-functions: introduced 1.166.44, fixed 1.166.48
- npm @tanstack/start-storage-context: introduced 1.166.38, fixed 1.166.42
- npm @tanstack/valibot-adapter: introduced 1.166.12, fixed 1.166.16
- npm @tanstack/virtual-file-routes: introduced 1.161.10, fixed 1.161.14
- npm @tanstack/vue-router: introduced 1.169.5, fixed 1.169.9
- npm @tanstack/vue-router-devtools: introduced 1.166.16, fixed 1.166.20
- npm @tanstack/vue-router-ssr-query: introduced 1.166.15, fixed 1.166.19
- npm @tanstack/vue-start: introduced 1.167.61, fixed 1.167.65
- npm @tanstack/vue-start-client: introduced 1.166.46, fixed 1.166.50
- npm @tanstack/vue-start-server: introduced 1.166.50, fixed 1.166.54
- npm @tanstack/zod-adapter: introduced 1.166.12, fixed 1.166.16
- npm @tanstack/arktype-adapter: introduced 1.166.15, fixed 1.166.16
- npm @tanstack/eslint-plugin-router: introduced 1.161.12, fixed 1.161.13
- npm @tanstack/eslint-plugin-start: introduced 0.0.7, fixed 0.0.8
- npm @tanstack/history: introduced 1.161.12, fixed 1.161.13
- npm @tanstack/nitro-v2-vite-plugin: introduced 1.154.15, fixed 1.154.16
- npm @tanstack/react-router: introduced 1.169.8, fixed 1.169.9
- npm @tanstack/react-router-devtools: introduced 1.166.19, fixed 1.166.20
- npm @tanstack/react-router-ssr-query: introduced 1.166.18, fixed 1.166.19
- npm @tanstack/react-start: introduced 1.167.71, fixed 1.167.72
- npm @tanstack/react-start-client: introduced 1.166.54, fixed 1.166.55
- npm @tanstack/react-start-rsc: introduced 0.0.50, fixed 0.0.51
- npm @tanstack/react-start-server: introduced 1.166.58, fixed 1.166.59
- npm @tanstack/router-cli: introduced 1.166.49, fixed 1.166.50
- npm @tanstack/router-core: introduced 1.169.8, fixed 1.169.9
- npm @tanstack/router-devtools: introduced 1.166.19, fixed 1.166.20
- npm @tanstack/router-devtools-core: introduced 1.167.9, fixed 1.167.10
- npm @tanstack/router-generator: introduced 1.166.48, fixed 1.166.49
- npm @tanstack/router-plugin: introduced 1.167.41, fixed 1.167.42
- npm @tanstack/router-ssr-query-core: introduced 1.168.6, fixed 1.168.7
- npm @tanstack/router-utils: introduced 1.161.14, fixed 1.161.15
- npm @tanstack/router-vite-plugin: introduced 1.166.56, fixed 1.166.57
- npm @tanstack/solid-router: introduced 1.169.8, fixed 1.169.9
- npm @tanstack/solid-router-devtools: introduced 1.166.19, fixed 1.166.20
- npm @tanstack/solid-router-ssr-query: introduced 1.166.18, fixed 1.166.19
- npm @tanstack/solid-start: introduced 1.167.68, fixed 1.167.69
- npm @tanstack/solid-start-client: introduced 1.166.53, fixed 1.166.54
- npm @tanstack/solid-start-server: introduced 1.166.57, fixed 1.166.58
- npm @tanstack/start-client-core: introduced 1.168.8, fixed 1.168.9
- npm @tanstack/start-fn-stubs: introduced 1.161.12, fixed 1.161.13
- npm @tanstack/start-plugin-core: introduced 1.169.26, fixed 1.169.27
- npm @tanstack/start-server-core: introduced 1.167.36, fixed 1.167.37
- npm @tanstack/start-static-server-functions: introduced 1.166.47, fixed 1.166.48
- npm @tanstack/start-storage-context: introduced 1.166.41, fixed 1.166.42
- npm @tanstack/valibot-adapter: introduced 1.166.15, fixed 1.166.16
- npm @tanstack/virtual-file-routes: introduced 1.161.13, fixed 1.161.14
- npm @tanstack/vue-router: introduced 1.169.8, fixed 1.169.9
- npm @tanstack/vue-router-devtools: introduced 1.166.19, fixed 1.166.20
- npm @tanstack/vue-router-ssr-query: introduced 1.166.18, fixed 1.166.19
- npm @tanstack/vue-start: introduced 1.167.64, fixed 1.167.65
- npm @tanstack/vue-start-client: introduced 1.166.49, fixed 1.166.50
- npm @tanstack/vue-start-server: introduced 1.166.53, fixed 1.166.54
- npm @tanstack/zod-adapter: introduced 1.166.15, fixed 1.166.16
Read on 2026-11-03T02:54:07.045Z under licence ghsa-cc-by-4.0@9e5f1b3c from https://api.osv.dev/v1/vulns/GHSA-g7cv-rxg3-hmpx
Defensive techniques (MITRE D3FEND)
D3FEND maps these defensive techniques to the weakness (CWE) that NVD lists for this CVE, through the digital artifacts the weakness affects. D3FEND does not say they stop this vulnerability.
CWE-506: Embedded Malicious Code
D3FEND lists no defensive technique for this weakness.
D3FEND ontology version 1.6.0.
Read on 2026-11-02T23:56:58.763Z under licence d3fend-terms-of-use@f98cbc7e from https://d3fend.mitre.org/api/weakness/cwe/CWE-506.json
MITRE D3FEND™ knowledge graph. © 2025 The MITRE Corporation.
"The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use D3FEND for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy." Terms: https://d3fend.mitre.org/tou/
Sources and licences
CISA
Source: CISA Catalog of Known Exploited Vulnerabilities, version 2026.10.30, CC0 1.0. Use of this data does not imply endorsement by CISA or DHS.
National Vulnerability Database (NIST)
This product uses the NVD API but is not endorsed or certified by the NVD.
NVD API Terms of Use (NIST publications in the public domain, 17 U.S.C. 105)
CVE Program, The MITRE Corporation
Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation. CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE™). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
GitHub Advisory Database
Source: GitHub Advisory Database, https://github.com/advisories/GHSA-g7cv-rxg3-hmpx, licensed under CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Changes: fields selected and reformatted by ransomware-tracker.com.
GitHub Advisory Database via OSV.dev
GHSA-g7cv-rxg3-hmpx: GitHub Advisory Database, https://github.com/advisories/GHSA-g7cv-rxg3-hmpx. Licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/), provided as is, without warranties. Retrieved via OSV.dev (https://osv.dev/vulnerability/GHSA-g7cv-rxg3-hmpx), which enriches records; fields selected and reformatted by ransomware-tracker.com.
MITRE D3FEND
MITRE D3FEND™ knowledge graph. © 2025 The MITRE Corporation.
"The MITRE Corporation (MITRE) hereby grants you a non-exclusive, royalty-free license to use D3FEND for research, development, and commercial purposes. Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy." Terms: https://d3fend.mitre.org/tou/MITRE D3FEND Terms of Use (site + knowledge graph); source repo MIT
Cite this page
Dragons Eye Ransomware Tracker, "CVE-2026-45321: TanStack Unspecified Vulnerability",
entity page, dataset version ref-b9296ea043f3, updated 2026-11-02T23:39:54.475Z,
https://ransomware-tracker.com/cve/CVE-2026-45321 (accessed 2026-11-03).
Underlying source: CISA Catalog of Known Exploited Vulnerabilities, version 2026.10.30.
Underlying source: National Vulnerability Database (NIST), CVE API 2.0, record last modified 2026-10-26T18:10:00.173.
Underlying source: CVE List (CVE Program, The MITRE Corporation), record updated 2026-08-04T03:56:09.005Z.
Underlying source: GitHub Advisory Database, GHSA-g7cv-rxg3-hmpx, updated 2026-06-08T23:53:12Z.
Underlying source: GitHub Advisory Database, GHSA-g7cv-rxg3-hmpx, via OSV.dev, modified 2026-09-10T03:51:05.608689266Z.
Underlying source: MITRE D3FEND, ontology version 1.6.0.
Pages change. The dataset version identifies the data, but no archive of old versions is kept, so this citation cannot be replayed later.