Skip to content
Server Security Center
KEVcritical9.6 Used in ransomware campaigns

CVE-2026-45321: TanStack Unspecified

TanStack · listed in the CISA catalog of actively exploited vulnerabilities since 2026-05-27.

CVSS v3.1 (CVE record)
9.6
critical
EPSS (exploit probability, 30 days)
3.3%
higher than 88.7% of all CVEs
Added to CISA KEV
2026-05-27
US federal due date 2026-06-10
Automatable (CISA SSVC)
no
technical impact: total

CVE-2026-45321 explained

CVE-2026-45321 is a supply-chain compromise of TanStack npm packages. On 2026-05-11, 84 malicious versions across 42 @tanstack/* packages were published to the npm registry under TanStack's legitimate trusted-publisher identity. These versions contain credential-stealing malware, so any system or build pipeline that installed them should be treated as potentially compromised.

Impact

Installing an affected version runs embedded malicious code designed to steal credentials. Exploitation is over the network and requires user interaction, such as installing or updating a package. The impact crosses component boundaries, with high impact on confidentiality, integrity and availability. CISA rates the technical impact as total but not automatable. CISA lists the vulnerability as known exploited and notes known use in ransomware campaigns.

Who is affected

Each affected package received exactly two malicious versions. Examples: @tanstack react-router 1.169.5 and 1.169.8, @tanstack history 1.161.9 and 1.161.12, @tanstack react-start 1.167.68 and 1.167.71, @tanstack react-start-server 1.166.55 and 1.166.58, and @tanstack eslint-plugin-start 0.0.4 and 0.0.7. The page lists 30 further products. The CVE record names no fixed version for any listed package.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • @tanstack arktype-adapter
    Affected
    • 1.166.12
    • 1.166.15
    Fixed in
    not stated
  • @tanstack eslint-plugin-router
    Affected
    • 1.161.9
    • 1.161.12
    Fixed in
    not stated
  • @tanstack eslint-plugin-start
    Affected
    • 0.0.4
    • 0.0.7
    Fixed in
    not stated
  • @tanstack history
    Affected
    • 1.161.9
    • 1.161.12
    Fixed in
    not stated
  • @tanstack nitro-v2-vite-plugin
    Affected
    • 1.154.12
    • 1.154.15
    Fixed in
    not stated
  • @tanstack react-router
    Affected
    • 1.169.5
    • 1.169.8
    Fixed in
    not stated
  • @tanstack react-router-devtools
    Affected
    • 1.166.16
    • 1.166.19
    Fixed in
    not stated
  • @tanstack react-router-ssr-query
    Affected
    • 1.166.15
    • 1.166.18
    Fixed in
    not stated
  • @tanstack react-start
    Affected
    • 1.167.68
    • 1.167.71
    Fixed in
    not stated
  • @tanstack react-start-client
    Affected
    • 1.166.51
    • 1.166.54
    Fixed in
    not stated
Show 32 more products
  • @tanstack react-start-rsc
    Affected
    • 0.0.47
    • 0.0.50
    Fixed in
    not stated
  • @tanstack react-start-server
    Affected
    • 1.166.55
    • 1.166.58
    Fixed in
    not stated
  • @tanstack router-cli
    Affected
    • 1.166.46
    • 1.166.49
    Fixed in
    not stated
  • @tanstack router-core
    Affected
    • 1.169.5
    • 1.169.8
    Fixed in
    not stated
  • @tanstack router-devtools
    Affected
    • 1.166.16
    • 1.166.19
    Fixed in
    not stated
  • @tanstack router-devtools-core
    Affected
    • 1.167.6
    • 1.167.9
    Fixed in
    not stated
  • @tanstack router-generator
    Affected
    • 1.166.45
    • 1.166.48
    Fixed in
    not stated
  • @tanstack router-plugin
    Affected
    • 1.167.38
    • 1.167.41
    Fixed in
    not stated
  • @tanstack router-ssr-query-core
    Affected
    • 1.168.3
    • 1.168.6
    Fixed in
    not stated
  • @tanstack router-utils
    Affected
    • 1.161.11
    • 1.161.14
    Fixed in
    not stated
  • @tanstack outer-vite-plugin
    Affected
    • 1.166.53
    • 1.166.56
    Fixed in
    not stated
  • @tanstack solid-router
    Affected
    • 1.169.5
    • 1.169.8
    Fixed in
    not stated
  • @tanstack solid-router-devtools
    Affected
    • 1.166.16
    • 1.166.19
    Fixed in
    not stated
  • @tanstack solid-router-ssr-query
    Affected
    • 1.166.15
    • 1.166.18
    Fixed in
    not stated
  • @tanstack solid-start
    Affected
    • 1.167.65
    • 1.167.68
    Fixed in
    not stated
  • @tanstack solid-start-client
    Affected
    • 1.166.50
    • 1.166.53
    Fixed in
    not stated
  • @tanstack solid-start-server
    Affected
    • 1.166.54
    • 1.166.57
    Fixed in
    not stated
  • @tanstack start-client-core
    Affected
    • 1.168.5
    • 1.168.8
    Fixed in
    not stated
  • @tanstack start-fn-stubs
    Affected
    • 1.161.9
    • 1.161.12
    Fixed in
    not stated
  • @tanstack start-plugin-core
    Affected
    • 1.169.23
    • 1.169.26
    Fixed in
    not stated
  • @tanstack start-server-core
    Affected
    • 1.167.33
    • 1.167.36
    Fixed in
    not stated
  • @tanstack start-static-server-functions
    Affected
    • 1.166.44
    • 1.166.47
    Fixed in
    not stated
  • @tanstack start-storage-context
    Affected
    • 1.166.38
    • 1.166.41
    Fixed in
    not stated
  • @tanstack valibot-adapter
    Affected
    • 1.166.12
    • 1.166.15
    Fixed in
    not stated
  • @tanstack virtual-file-routes
    Affected
    • 1.161.10
    • 1.161.13
    Fixed in
    not stated
  • @tanstack vue-router
    Affected
    • 1.169.5
    • 1.169.8
    Fixed in
    not stated
  • @tanstack vue-router-devtools
    Affected
    • 1.166.16
    • 1.166.19
    Fixed in
    not stated
  • @tanstack vue-router-ssr-query
    Affected
    • 1.166.15
    • 1.166.18
    Fixed in
    not stated
  • @tanstack vue-start
    Affected
    • 1.167.61
    • 1.167.64
    Fixed in
    not stated
  • @tanstack vue-start-client
    Affected
    • 1.166.46
    • 1.166.49
    Fixed in
    not stated
  • @tanstack vue-start-server
    Affected
    • 1.166.50
    • 1.166.53
    Fixed in
    not stated
  • @tanstack zod-adapter
    Affected
    • 1.166.12
    • 1.166.15
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: github.com/TanStack/router/security/advisories/GHSA-g7cv-…
  • CISA's deadline for US federal agencies: 2026-06-10 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Check lockfiles, caches and build logs for any of the malicious @tanstack/* versions listed in the CVE record.
  2. Remove affected versions and pin dependencies to versions not listed as malicious, following the TanStack advisory.
  3. Treat systems and CI runners that installed affected versions as compromised and investigate them for signs of compromise.
  4. Rotate credentials, tokens and secrets that were accessible on affected developer machines or build environments.
  5. Apply the vendor's mitigations as CISA requires, and follow BOD 22-01 guidance for cloud services where applicable.

The CVE record names no fixed version. Follow the TanStack advisory for guidance on safe versions. Avoid the malicious versions listed in the record. CISA requires applying mitigations per vendor instructions, or discontinuing use of the product if mitigations are unavailable. Rotate any exposed credentials in the meantime.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-506 Embedded Malicious Code

Questions about CVE-2026-45321

Is every version of the @tanstack packages affected?
No. The CVE record lists exactly two malicious versions per affected package, published a few minutes apart on 2026-05-11. Check whether your projects installed one of those specific versions.
Is this vulnerability being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-05-27 and notes known ransomware use. The US federal due date is 2026-06-10.
What should I do if an affected version was installed?
The malware steals credentials. Treat the affected machines and build pipelines as compromised. Rotate all secrets they could access, remove the malicious versions, and follow the vendor advisory.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.