ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-45321

TanStack Unspecified Vulnerability

Published May 11, 2026 · catalog updated Jun 17, 2026 · TanStack Unspecified

Patch now

CVE-2026-45321 is in the CISA known-exploited catalog, due Jun 10, 2026. Confirm TanStack Unspecified against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (TanStack Unspecified).
Severity
Critical9.6
Known exploitation
CISA KEV and VulnCheck KEV
EPSS
1.05%
Remediation
Remediation guidance
Affected products
cpe tanstack/tanstack/arktype-adapter · cpe tanstack/tanstack/eslint-plugin-router · cpe tanstack/tanstack/eslint-plugin-start · cpe tanstack/tanstack/history · cpe tanstack/tanstack/nitro-v2-vite-plugin · cpe tanstack/tanstack/react-router

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • 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

How to fix CVE-2026-45321

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2026-45321 is in the CISA known-exploited catalog, due Jun 10, 2026. Confirm TanStack Unspecified against the vendor advisory and apply that fix. The CVSS score does not change the priority.

Which versions are affected?

Compare what you have installed with 1.166.12, 1.166.15, 1.161.12, 1.161.9, 0.0.4, 0.0.7. 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 should an analyst verify?

CWE-506. EPSS 1.05%. The CISA KEV listing is the exploitation evidence. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. 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

  2. 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.

  3. 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.

  4. 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

  5. Jun 17, 2026 · NIST NVD

    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

Sources

  • CISA KEVConfirmed exploitationCVE-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.orgVulnerability recordCVE-2026-45321

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-45321

    30-day exploitation probability 1.1%

    first.org
  • NIST NVDVulnerability recordCVE-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
  • VulnCheck KEVConfirmed exploitationCVE-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.

    vulncheck.com

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.