TanStack · TanStack · published 2026-05-12

CVE-2026-45321TanStack Unspecified Vulnerability

Patch today Known exploited and used in ransomware campaigns.

CVE-2026-45321 is actively exploited in the wild: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-27, and it is known to be used in ransomware campaigns. EPSS estimates a 3.3% chance of exploitation in the next 30 days, higher than 88% of all CVEs. This TanStack vulnerability: CVSS 9.6 (v3.1), a successful attack gives total control of the component. CISA’s 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. US federal agencies must remediate by 2026-06-10. Patch today.

Share this

Remediation#

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. (federal due date 2026-06-10)

Patch events

  1. Patch todayExploited (KEV)CISA due 2026-06-10

    Other softwareTanStack

    UnspecifiedCVE-2026-45321

    Why: Known exploited and used in ransomware campaigns.

Exploit intelligence#

SignalValueSource
Known exploitedYes, added 2026-05-27CISA KEV
Ransomware useKnownCISA KEV
EPSS (30-day exploitation probability)3.3% (89th pct)FIRST EPSS v2026.06.15
CVSS base score9.6 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
CNA / CISA ADP
SSVC exploitationactiveCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impacttotalCISA Vulnrichment

More from this vendor: all TanStack vulnerabilities · recent KEV additions

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →