CVE-2026-45321: TanStack Unspecified Vulnerability

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-05-12).

Weakness: CWE-506: Embedded Malicious Code

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: total.

On CISA KEV since

2026-05-27

US federal deadline

2026-06-10

Ransomware use

Yes

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-06725, EUVD-2026-29352, GHSA-g7cv-rxg3-hmpx

VEDAS cluster: VEDAS:GAZELLEGRAY

Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (3)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

• Code repository: https://github.com/7whyex/cve-2026-45321-tanstack
• Code repository: https://github.com/adriannurrr/cve-2026-45321-tanstack
• Code repository: https://github.com/renewablehacking/cve-2026-45321-tanstack

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

• Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-29352
• Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-g7cv-rxg3-hmpx
• Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-45321
• Vulnerability database or vendor advisory: https://osv.dev/vulnerability/CVE-2026-45321
• Vulnerability database or vendor advisory: https://osv.dev/vulnerability/GHSA-g7cv-rxg3-hmpx
• Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-45321

17 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS

0.033
some chance of attack soon

VEDAS

0.973
strong exploit evidence

On CISA KEV

Yes, since 2026-05-27

Detection rule

None yet

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

22 more products are listed in the CVE record.

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: tanstack tanstack\/arktype-adapter, tanstack tanstack\/eslint-plugin-router, tanstack tanstack\/eslint-plugin-start, tanstack tanstack\/history, tanstack tanstack\/nitro-v2-vite-plugin, tanstack tanstack\/react-router, tanstack tanstack\/react-router-devtools, tanstack tanstack\/react-router-ssr-query, tanstack tanstack\/react-start, tanstack tanstack\/react-start-client.

How to fix it

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

Vendor guidance:

• https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx
• https://nvd.nist.gov/vuln/detail/CVE-2026-45321

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

Advisories on this CVE

• TanStack to Nx Console to GitHub: one poisoned npm install led to ~3,800 stolen internal repos (CVE-2026-45321, CVE-2026-48027) (full advisory)
• TanStack npm compromise (CVE-2026-45321, GHSA-g7cv-rxg3-hmpx) (11 May 2026)

References

Government sources

• https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-45321 (government-resource)

Other references

• https://github.com/TanStack/router/security/advisories/GHSA-g7cv-rxg3-hmpx (x_refsource_CONFIRM)
• https://github.com/TanStack/router/issues/7383 (x_refsource_MISC)
• https://tanstack.com/blog/npm-supply-chain-compromise-postmortem (x_refsource_MISC)
• https://www.stepsecurity.io/blog/mini-shai-hulud-is-back-a-self-spreading-supply-chain-attack-hits-the-npm-ecosystem (x_refsource_MISC)

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.