CVE-2026-45321 is a critical-severity flaw (CVSS 9.6) affecting tanstack\/arktype-adapter, tanstack\/eslint-plugin-router, tanstack\/eslint-plugin-start, reported as exploited in the wild. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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 po
Verify at the official sourceNVD · CVE Program · CISA KEV catalog · Report a problem with this page Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-45321?
tanstack\/arktype-adapter: downgrade or apply the listed mitigation; tanstack\/eslint-plugin-router: downgrade or apply the listed mitigation; tanstack\/eslint-plugin-start: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2026-45321 being exploited?
Yes. CVE-2026-45321 is on the CISA Known Exploited Vulnerabilities list, so treat it as patch-now.
What does CVE-2026-45321 affect?
CVE-2026-45321 affects tanstack\/arktype-adapter, tanstack\/eslint-plugin-router, tanstack\/eslint-plugin-start. Severity is critical (CVSS 9.6). 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 bin
How urgent is CVE-2026-45321?
Priority 91/100. Critical severity; Exploited in the wild (CISA KEV); Used in ransomware campaigns; Public exploit reference