CVE-2026-45321

CRITICALNVD 9.69.6—
EchelonGraph scoreHIGH confidence

Score elevated to 9.6 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-05-27), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.6 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Exploited in the wild
9.6EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 1.1%CVSS: 9.6Exploit: cisa kev · ssvc active · kev ransomware · public exploitExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.6
EG Score
9.6CRITICALhigh confidence
EG Risk
83
EG Risk 83/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
1.1%
EPSS %ILE
63rd
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

May 12, 2026

Last Modified

August 4, 2026

Advisory Details (5)

Auto-updated Oct 7, 2026
Patch available. Sources: github.
generic

TeamPCP's Mini Shai-Hulud Is Back: A Self-Spreading Supply Chain Attack Compromises TanStack npm Packages - StepSecurity

https://www.stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem
generic

Postmortem: TanStack npm supply-chain compromise | TanStack Blog

https://tanstack.com/blog/npm-supply-chain-compromise-postmortem
generic

Several npm latest releases were compromised · Issue #7383 · TanStack/router · GitHub

https://github.com/TanStack/router/issues/7383
githubMentions a patch (unverified)

Malware in 42 @tanstack/* packages exfiltrates cloud credentials, GitHub tokens, and SSH keys · Advisory · TanStack/router · GitHub

https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx
cisa🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-45321

Vendor Advisories for CVE-2026-45321(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(42 across 1 ecosystem)
npm(42)
PackageVulnerable rangeFix by version rangeDependents
@tanstack/arktype-adapter1.166.15
  • 1.166.12 up to 1.166.16: fixed in 1.166.16
  • 1.166.15 up to 1.166.16: fixed in 1.166.16
—
@tanstack/eslint-plugin-router1.161.12
  • 1.161.9 up to 1.161.13: fixed in 1.161.13
  • 1.161.12 up to 1.161.13: fixed in 1.161.13
—
@tanstack/eslint-plugin-start0.0.7
  • 0.0.4 up to 0.0.8: fixed in 0.0.8
  • 0.0.7 up to 0.0.8: fixed in 0.0.8
—
@tanstack/history1.161.12
  • 1.161.9 up to 1.161.13: fixed in 1.161.13
  • 1.161.12 up to 1.161.13: fixed in 1.161.13
—
@tanstack/nitro-v2-vite-plugin1.154.15
  • 1.154.12 up to 1.154.16: fixed in 1.154.16
  • 1.154.15 up to 1.154.16: fixed in 1.154.16
—
@tanstack/react-router1.169.8
  • 1.169.5 up to 1.169.9: fixed in 1.169.9
  • 1.169.8 up to 1.169.9: fixed in 1.169.9
—
@tanstack/react-router-devtools1.166.19
  • 1.166.16 up to 1.166.20: fixed in 1.166.20
  • 1.166.19 up to 1.166.20: fixed in 1.166.20
—
@tanstack/react-router-ssr-query1.166.18
  • 1.166.15 up to 1.166.19: fixed in 1.166.19
  • 1.166.18 up to 1.166.19: fixed in 1.166.19
—
@tanstack/react-start1.167.71
  • 1.167.68 up to 1.167.72: fixed in 1.167.72
  • 1.167.71 up to 1.167.72: fixed in 1.167.72
—
@tanstack/react-start-client1.166.54
  • 1.166.51 up to 1.166.55: fixed in 1.166.55
  • 1.166.54 up to 1.166.55: fixed in 1.166.55
—
@tanstack/react-start-rsc0.0.50
  • 0.0.47 up to 0.0.51: fixed in 0.0.51
  • 0.0.50 up to 0.0.51: fixed in 0.0.51
—
@tanstack/react-start-server1.166.58
  • 1.166.55 up to 1.166.59: fixed in 1.166.59
  • 1.166.58 up to 1.166.59: fixed in 1.166.59
—
@tanstack/router-cli1.166.49
  • 1.166.46 up to 1.166.50: fixed in 1.166.50
  • 1.166.49 up to 1.166.50: fixed in 1.166.50
—
@tanstack/router-core1.169.8
  • 1.169.5 up to 1.169.9: fixed in 1.169.9
  • 1.169.8 up to 1.169.9: fixed in 1.169.9
—
@tanstack/router-devtools1.166.19
  • 1.166.16 up to 1.166.20: fixed in 1.166.20
  • 1.166.19 up to 1.166.20: fixed in 1.166.20
—
@tanstack/router-devtools-core1.167.9
  • 1.167.6 up to 1.167.10: fixed in 1.167.10
  • 1.167.9 up to 1.167.10: fixed in 1.167.10
—
@tanstack/router-generator1.166.48
  • 1.166.45 up to 1.166.49: fixed in 1.166.49
  • 1.166.48 up to 1.166.49: fixed in 1.166.49
—
@tanstack/router-plugin1.167.41
  • 1.167.38 up to 1.167.42: fixed in 1.167.42
  • 1.167.41 up to 1.167.42: fixed in 1.167.42
—
@tanstack/router-ssr-query-core1.168.6
  • 1.168.3 up to 1.168.7: fixed in 1.168.7
  • 1.168.6 up to 1.168.7: fixed in 1.168.7
—
@tanstack/router-utils1.161.14
  • 1.161.11 up to 1.161.15: fixed in 1.161.15
  • 1.161.14 up to 1.161.15: fixed in 1.161.15
—
@tanstack/router-vite-plugin1.166.56
  • 1.166.53 up to 1.166.57: fixed in 1.166.57
  • 1.166.56 up to 1.166.57: fixed in 1.166.57
—
@tanstack/solid-router1.169.8
  • 1.169.5 up to 1.169.9: fixed in 1.169.9
  • 1.169.8 up to 1.169.9: fixed in 1.169.9
—
@tanstack/solid-router-devtools1.166.19
  • 1.166.16 up to 1.166.20: fixed in 1.166.20
  • 1.166.19 up to 1.166.20: fixed in 1.166.20
—
@tanstack/solid-router-ssr-query1.166.18
  • 1.166.15 up to 1.166.19: fixed in 1.166.19
  • 1.166.18 up to 1.166.19: fixed in 1.166.19
—
@tanstack/solid-start1.167.68
  • 1.167.65 up to 1.167.69: fixed in 1.167.69
  • 1.167.68 up to 1.167.69: fixed in 1.167.69
—
@tanstack/solid-start-client1.166.53
  • 1.166.50 up to 1.166.54: fixed in 1.166.54
  • 1.166.53 up to 1.166.54: fixed in 1.166.54
—
@tanstack/solid-start-server1.166.57
  • 1.166.54 up to 1.166.58: fixed in 1.166.58
  • 1.166.57 up to 1.166.58: fixed in 1.166.58
—
@tanstack/start-client-core1.168.8
  • 1.168.5 up to 1.168.9: fixed in 1.168.9
  • 1.168.8 up to 1.168.9: fixed in 1.168.9
—
@tanstack/start-fn-stubs1.161.12
  • 1.161.9 up to 1.161.13: fixed in 1.161.13
  • 1.161.12 up to 1.161.13: fixed in 1.161.13
—
@tanstack/start-plugin-core1.169.26
  • 1.169.23 up to 1.169.27: fixed in 1.169.27
  • 1.169.26 up to 1.169.27: fixed in 1.169.27
—
@tanstack/start-server-core1.167.36
  • 1.167.33 up to 1.167.37: fixed in 1.167.37
  • 1.167.36 up to 1.167.37: fixed in 1.167.37
—
@tanstack/start-static-server-functions1.166.47
  • 1.166.44 up to 1.166.48: fixed in 1.166.48
  • 1.166.47 up to 1.166.48: fixed in 1.166.48
—
@tanstack/start-storage-context1.166.41
  • 1.166.38 up to 1.166.42: fixed in 1.166.42
  • 1.166.41 up to 1.166.42: fixed in 1.166.42
—
@tanstack/valibot-adapter1.166.15
  • 1.166.12 up to 1.166.16: fixed in 1.166.16
  • 1.166.15 up to 1.166.16: fixed in 1.166.16
—
@tanstack/virtual-file-routes1.161.13
  • 1.161.10 up to 1.161.14: fixed in 1.161.14
  • 1.161.13 up to 1.161.14: fixed in 1.161.14
—
@tanstack/vue-router1.169.8
  • 1.169.5 up to 1.169.9: fixed in 1.169.9
  • 1.169.8 up to 1.169.9: fixed in 1.169.9
—
@tanstack/vue-router-devtools1.166.19
  • 1.166.16 up to 1.166.20: fixed in 1.166.20
  • 1.166.19 up to 1.166.20: fixed in 1.166.20
—
@tanstack/vue-router-ssr-query1.166.18
  • 1.166.15 up to 1.166.19: fixed in 1.166.19
  • 1.166.18 up to 1.166.19: fixed in 1.166.19
—
@tanstack/vue-start1.167.64
  • 1.167.61 up to 1.167.65: fixed in 1.167.65
  • 1.167.64 up to 1.167.65: fixed in 1.167.65
—
@tanstack/vue-start-client1.166.49
  • 1.166.46 up to 1.166.50: fixed in 1.166.50
  • 1.166.49 up to 1.166.50: fixed in 1.166.50
—
@tanstack/vue-start-server1.166.53
  • 1.166.50 up to 1.166.54: fixed in 1.166.54
  • 1.166.53 up to 1.166.54: fixed in 1.166.54
—
@tanstack/zod-adapter1.166.15
  • 1.166.12 up to 1.166.16: fixed in 1.166.16
  • 1.166.15 up to 1.166.16: fixed in 1.166.16
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 64× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 284 total refreshes for this CVE.

  1. 2026-10-09 21:14 UTCEG score recompute
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 18:38 UTCEG score recompute
  4. 2026-10-08 17:12 UTCEPSS rescore
  5. 2026-10-08 03:25 UTCEG score recompute
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-06 17:19 UTCEG score recompute
  8. 2026-10-06 15:18 UTCEPSS rescore
  9. 2026-10-05 18:28 UTCEG score recompute
  10. 2026-10-05 17:43 UTCEPSS rescore
  11. 2026-10-04 23:31 UTCEG score recompute
  12. 2026-10-04 23:22 UTCEPSS rescore
  13. 2026-10-03 17:12 UTCEG score recompute
  14. 2026-10-03 14:25 UTCEPSS rescore
  15. 2026-10-02 18:22 UTCEG score recompute
  16. 2026-10-01 23:26 UTCEG score recompute
  17. 2026-10-01 19:50 UTCEPSS rescore
  18. 2026-09-30 17:08 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescore
  20. 2026-09-29 18:20 UTCEG score recompute
  21. 2026-09-28 23:24 UTCEG score recompute
  22. 2026-09-28 15:49 UTCEG score recompute
  23. 2026-09-27 21:51 UTCCISA KEV update
  24. 2026-09-27 17:05 UTCEG score recompute
  25. 2026-09-27 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-09-26 18:21 UTCEG score recompute
  2. 2026-09-26 15:58 UTCEPSS rescore
  3. 2026-09-26 03:08 UTCEG score recompute
  4. 2026-09-25 19:35 UTCCISA KEV update
  5. 2026-09-25 14:55 UTCCISA KEV update
  6. 2026-09-24 19:31 UTCCISA KEV update
  7. 2026-09-24 17:02 UTCEG score recompute
  8. 2026-09-23 18:17 UTCEG score recompute
  9. 2026-09-23 17:53 UTCEPSS rescore
  10. 2026-09-22 19:36 UTCCISA KEV update
  11. 2026-09-22 15:43 UTCEG score recompute
  12. 2026-09-22 00:34 UTCEG score recompute
  13. 2026-09-21 19:09 UTCCISA KEV update
  14. 2026-09-20 22:05 UTCEG score recompute
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-19 15:45 UTCEG score recompute
  17. 2026-09-18 20:43 UTCEG score recompute
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-18 19:20 UTCCISA KEV update
  20. 2026-09-18 14:15 UTCCISA KEV update
  21. 2026-09-17 21:59 UTCEG score recompute
  22. 2026-09-17 19:31 UTCEPSS rescore
  23. 2026-09-16 15:40 UTCEG score recompute
  24. 2026-09-16 14:10 UTCCISA KEV update
  25. 2026-09-16 14:08 UTCEPSS rescore
  26. 2026-09-16 08:05 UTCEG score recompute
  27. 2026-09-16 05:15 UTCEPSS rescore
  28. 2026-09-15 05:30 UTCEG score recompute
  29. 2026-09-14 19:24 UTCCISA KEV update
  30. 2026-09-13 19:23 UTCEG score recompute
  31. 2026-09-13 16:47 UTCEPSS rescore
  32. 2026-09-12 16:51 UTCEG score recompute
  33. 2026-09-12 15:01 UTCEPSS rescore
  34. 2026-09-11 18:49 UTCCISA KEV update
  35. 2026-09-11 18:08 UTCEG score recompute
  36. 2026-09-11 14:53 UTCEPSS rescore
  37. 2026-09-11 10:34 UTCEG score recompute
  38. 2026-09-11 09:37 UTCEPSS rescore
  39. 2026-09-10 19:28 UTCCISA KEV update
  40. 2026-09-10 11:51 UTCEG score recompute
  41. 2026-09-10 09:34 UTCEPSS rescore
  42. 2026-09-09 19:08 UTCCISA KEV update
  43. 2026-09-09 01:41 UTCEG score recompute
  44. 2026-09-08 22:00 UTCEPSS rescore
  45. 2026-09-08 18:54 UTCCISA KEV update
  46. 2026-09-07 19:18 UTCEG score recompute
  47. 2026-09-07 16:01 UTCEPSS rescore
  48. 2026-09-06 16:43 UTCEG score recompute
  49. 2026-09-06 13:47 UTCEPSS rescore
  50. 2026-09-05 17:57 UTCEG score recompute
  51. 2026-09-04 17:38 UTCCISA KEV update
  52. 2026-09-04 15:18 UTCEG score recompute
  53. 2026-09-04 07:45 UTCEG score recompute
  54. 2026-09-04 05:06 UTCEPSS rescore
  55. 2026-09-02 17:40 UTCEG score recompute
  56. 2026-09-02 17:33 UTCCISA KEV update
  57. 2026-09-02 14:12 UTCEPSS rescore
  58. 2026-09-01 14:59 UTCEG score recompute
  59. 2026-09-01 13:54 UTCEPSS rescore
  60. 2026-09-01 07:23 UTCEG score recompute
  61. 2026-08-31 14:19 UTCCISA KEV update
  62. 2026-08-30 21:13 UTCEG score recompute
  63. 2026-08-30 19:17 UTCEPSS rescore
  64. 2026-08-30 02:14 UTCEG score recompute
  65. 2026-08-30 01:22 UTCEPSS rescore
  66. 2026-08-28 23:39 UTCEG score recompute
  67. 2026-08-28 21:41 UTCEPSS rescore
  68. 2026-08-27 17:22 UTCCISA KEV update
  69. 2026-08-27 17:15 UTCEG score recompute
  70. 2026-08-27 14:25 UTCEPSS rescore
  71. 2026-08-26 18:28 UTCEG score recompute
  72. 2026-08-26 17:41 UTCCISA KEV update
  73. 2026-08-26 14:46 UTCEPSS rescore
  74. 2026-08-25 15:56 UTCEG score recompute
  75. 2026-08-25 13:49 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCfabriziosalmi/tanstack-compromise-checker
    First seen May 16, 2026

    Shell script to detect TanStack npm supply chain attack indicators (CVE-2026-45321 / GHSA-g7cv-rxg3-hmpx)

    Open source ↗
  • GitHub PoCIntrudify/mini-shai-hulud-scanner
    First seen May 13, 2026

    Scanner for the Mini Shai-Hulud npm/PyPI supply chain worm (NHS CC-4781 · CVE-2026-45321). Detects gh-token-monitor persistence, payload artefacts, and attacker commits. Python, Bash, PowerShell.

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2026-45321?
CVE-2026-45321 is a critical vulnerability published on May 12, 2026. 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…
When was CVE-2026-45321 disclosed?
CVE-2026-45321 was first published on May 12, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45321 actively exploited?
Yes. CISA added CVE-2026-45321 to the Known Exploited Vulnerabilities catalog on May 27, 2026, affecting TanStack TanStack. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2026-45321?
CVE-2026-45321 has a CVSS v3 base score of 9.6 (NVD).
Which products are affected by CVE-2026-45321?
CVE-2026-45321 affects TanStack TanStack. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2026-45321?
A fix for CVE-2026-45321 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45321 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45321

Explore →

Is Your Infrastructure Affected by CVE-2026-45321?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs