Back to live map

CVE-2026-45321

KEVRansomware UseTanStack 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.

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.

CVSS 3.1 vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
PublishedMay 12, 2026
Last modifiedOct 26, 2026
Added to KEVMay 27, 2026
Remediation dueJun 10, 2026
    88
    Risk assessment · Critical

    Actively exploited and used by ransomware crews. Patch immediately.

    Exploitation
    Confirmed in the wild (CISA KEV)
    Federal remediation deadline
    Overdue by 139 days
    Ransomware
    Used in known ransomware campaigns
    CVSS
    9.6 CRITICAL
    EPSS (30-day exploit probability)
    3.3% · top 12% of all CVEs
    Weakness
    CWE-506
    Attack vector
    Network, remotely reachable
    1. 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
    2. 2.Treat as emergency change: patch or isolate internet-facing instances first.
    3. 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
    4. 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
    5. 5.Verify offline/immutable backups and segment the affected systems. This flaw is used for ransomware initial access.

    Assessment is derived automatically from the live signals above; verify against your own asset inventory.