On 2026-05-27, CISA added CVE-2026-45321 (TanStack TanStack) to its Known Exploited Vulnerabilities (KEV) catalog [2]. The vulnerability is listed in the catalog as "TanStack Unspecified Vulnerability" [2]. CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Backfill: this event became public on May 27, 2026 and we added it on Nov 10, 2026. It is not a new event.
CISA Adds TanStack TanStack Vulnerability CVE-2026-45321 to Known Exploited Vulnerabilities Catalog
1 min read
- Disclosed
- May 27, 2026
- Published
- Nov 10, 2026
- Last updated
- Nov 8, 2026
- CVSS basis
- Our assessment
- 3.3%, higher than 89% of CVEs
- Exploitation and patch status
- ExploitedKEV
- Attack vector
- Vulnerability status
- Actor type
- Motivation
On this page
30-second summary
What happened
Who is affected
Industries mainly affected: Government, Cross-industry
What to do nowOur advice
CISA requires remediation in accordance with the listed vendor mitigation guidance; see the original text in the body for specific requirements [2].
Timeline
Technical details
CISA KEV Listing Record
CISA added CVE-2026-45321 (TanStack TanStack) to the Known Exploited Vulnerabilities () catalog on 2026-05-27 [2].
Original Technical Description
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. [2]
Official 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. [2]
Individual Vulnerability Record
The U.S. National Vulnerability Database (NVD) provides an independent vulnerability record and description for CVE-2026-45321 [1].
References
Official / primary3
- [1]
“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 wa”
- [2]
This site aggregates public information and is not security consulting advice. Test remediation steps before applying.