CVE-2026-45321
TanStack Unspecified Vulnerability
Published May 11, 2026 · updated Jun 17, 2026 · TanStack TanStack
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.
Timeline
Detection, updates, and resolution for this record.
May 11, 2026 · Catalog
Detected
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
May 27, 2026 · CISA KEV
Known exploited
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Jun 10, 2026 · CISA KEV
Remediation due
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Jun 17, 2026 · Catalog
Updated
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
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 due date Jun 10, 2026
Affected
- cpe tanstack/tanstack/arktype-adapter1.166.12
- cpe tanstack/tanstack/arktype-adapter1.166.15
- cpe tanstack/tanstack/eslint-plugin-router1.161.12
- cpe tanstack/tanstack/eslint-plugin-router1.161.9
- cpe tanstack/tanstack/eslint-plugin-start0.0.4
- cpe tanstack/tanstack/eslint-plugin-start0.0.7
- cpe tanstack/tanstack/history1.161.12
- cpe tanstack/tanstack/history1.161.9
- cpe tanstack/tanstack/nitro-v2-vite-plugin1.154.12
- cpe tanstack/tanstack/react-router1.169.5
- cpe tanstack/tanstack/react-router-devtools1.166.16
- cpe tanstack/tanstack/react-router-ssr-query1.166.15
- vendor TanStack TanStackversion unspecified
Sources
- CISA KEVCVE-2026-45321
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.gov - CVE.orgCVE-2026-45321
Official CVE identifier
cve.org - FIRST EPSSCVE-2026-45321
30-day exploitation probability 1.1%
first.org - NIST NVDCVE-2026-45321
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 publis
nvd.nist.gov