CONTENTUM.COMA specialist. A plan. A result.

Exploited vulnerabilities · TanStack

CVE-2026-45321
TanStack Unspecified Vulnerability

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.

Description in the NVD

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.

Required action according to CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

What to do now

  • Check your exposureFind out whether TanStack TanStack runs anywhere in your environment, including systems of suppliers.
  • Patch or mitigateApply the vendor update. If that is not possible at once, use the vendor's mitigation or take the system off the network.
  • Look for signs of an attackThis vulnerability is exploited in real attacks. Review the logs of affected systems for the time before the patch.

References

Data: CISA Known Exploited Vulnerabilities Catalog and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.