CVE-2026-45321
CVE-2026-45321 is a critical-severity vulnerability (CVSS 3.1 base score 9.6). 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. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-27, with a remediation due date of 2026-06-10 for US federal civilian agencies. CISA lists known use in ransomware campaigns. As of 2026-11-22, EPSS estimates a 3.3% probability of exploitation in the next 30 days, in the 88th percentile of scored CVEs.
Updated
- CVSS 3.1
- 9.6 CRITICAL
- EPSS
- 3.3% (88th pct)
- CISA KEV
- Exploited
- Published
- 2026-05-12
- Weakness
- CWE-506
TanStack Unspecified Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
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
This vulnerability could affect an open-source component, third-party library, protocol, or proprietary implementation that could be used by different products. For more information, please see: https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx ; https://nvd.nist.gov/vuln/detail/CVE-2026-45321
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.
Key Findings
as of 2026-11-22- CISA added CVE-2026-45321 to the KEV catalog 16 days after its CVE record was published. The median for entries added in 2026 so far is 12.5 days.
- Its current EPSS score (3.3%) is higher than that of 12% of CISA KEV entries.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact total, 2026-05-27).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet. Forensic triage means assessing the asset to determine whether it has been compromised.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| @tanstack | @tanstack arktype-adapter | 1.166.12 1.166.15 |
| @tanstack | @tanstack eslint-plugin-router | 1.161.9 1.161.12 |
| @tanstack | @tanstack eslint-plugin-start | 0.0.4 0.0.7 |
| @tanstack | @tanstack history | 1.161.9 1.161.12 |
| @tanstack | @tanstack nitro-v2-vite-plugin | 1.154.12 1.154.15 |
| @tanstack | @tanstack react-router | 1.169.5 1.169.8 |
| @tanstack | @tanstack react-router-devtools | 1.166.16 1.166.19 |
| @tanstack | @tanstack react-router-ssr-query | 1.166.15 1.166.18 |
| @tanstack | @tanstack react-start | 1.167.68 1.167.71 |
| @tanstack | @tanstack react-start-client | 1.166.51 1.166.54 |
| @tanstack | @tanstack react-start-rsc | 0.0.47 0.0.50 |
| @tanstack | @tanstack react-start-server | 1.166.55 1.166.58 |
| @tanstack | @tanstack router-cli | 1.166.46 1.166.49 |
| @tanstack | @tanstack router-core | 1.169.5 1.169.8 |
| @tanstack | @tanstack router-devtools | 1.166.16 1.166.19 |
| @tanstack | @tanstack router-devtools-core | 1.167.6 1.167.9 |
| @tanstack | @tanstack router-generator | 1.166.45 1.166.48 |
| @tanstack | @tanstack router-plugin | 1.167.38 1.167.41 |
| @tanstack | @tanstack router-ssr-query-core | 1.168.3 1.168.6 |
| @tanstack | @tanstack router-utils | 1.161.11 1.161.14 |
| @tanstack | @tanstack outer-vite-plugin | 1.166.53 1.166.56 |
| @tanstack | @tanstack solid-router | 1.169.5 1.169.8 |
| @tanstack | @tanstack solid-router-devtools | 1.166.16 1.166.19 |
| @tanstack | @tanstack solid-router-ssr-query | 1.166.15 1.166.18 |
| @tanstack | @tanstack solid-start | 1.167.65 1.167.68 |
| @tanstack | @tanstack solid-start-client | 1.166.50 1.166.53 |
| @tanstack | @tanstack solid-start-server | 1.166.54 1.166.57 |
| @tanstack | @tanstack start-client-core | 1.168.5 1.168.8 |
| @tanstack | @tanstack start-fn-stubs | 1.161.9 1.161.12 |
| @tanstack | @tanstack start-plugin-core | 1.169.23 1.169.26 |
| @tanstack | @tanstack start-server-core | 1.167.33 1.167.36 |
| @tanstack | @tanstack start-static-server-functions | 1.166.44 1.166.47 |
| @tanstack | @tanstack start-storage-context | 1.166.38 1.166.41 |
| @tanstack | @tanstack valibot-adapter | 1.166.12 1.166.15 |
| @tanstack | @tanstack virtual-file-routes | 1.161.10 1.161.13 |
| @tanstack | @tanstack vue-router | 1.169.5 1.169.8 |
| @tanstack | @tanstack vue-router-devtools | 1.166.16 1.166.19 |
| @tanstack | @tanstack vue-router-ssr-query | 1.166.15 1.166.18 |
| @tanstack | @tanstack vue-start | 1.167.61 1.167.64 |
| @tanstack | @tanstack vue-start-client | 1.166.46 1.166.49 |
| @tanstack | @tanstack vue-start-server | 1.166.50 1.166.53 |
| @tanstack | @tanstack zod-adapter | 1.166.12 1.166.15 |
References
4 linksOther 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
Record Details
- Published
- 2026-05-12
- Last updated
- 2026-08-04
- Assigner (CNA)
- GitHub_M
- Credited to
- -
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.