TanStack Unspecified

What to do

1. Check which version of arktype-adapter you run against the affected versions below, and install the vendor's latest release.
2. 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.
3. Read the advisory on github.com for workarounds and exact fixed builds.
4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
5. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

Version data comes from the organisation that assigned the CVE; 35 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector

NetworkCan be exploited remotely over a network, including the internet.

Attack complexity

LowNo special conditions are needed; the attack works reliably.

Privileges required

NoneNo account or login is needed.

User interaction

RequiredA user must take an action such as opening a file or link.

Scope

ChangedThe attack can reach beyond the vulnerable component into other systems.

Confidentiality

HighAll data handled by the component can be read.

Integrity

HighData or code can be modified at will.

Availability

HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H. Scored by CNA (github.com).

Official description

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Embedded Malicious Code

Timeline

1. May 12, 2026CVE record published.
2. May 27, 2026CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
3. May 27, 2026Added to CISA's Known Exploited Vulnerabilities catalogue.
4. June 10, 2026Deadline for US federal agencies to remediate, set by CISA.
5. October 26, 2026Record last changed materially (score, affected products, status or references).

References

Recent Embedded Malicious Code vulnerabilities

• 9.8 Critical severity

  Accordion and Accordion Slider: Embedded Malicious Code

  CVE-2026-6443Apr 17, 2026Essentialplugin
• 9.8 Critical severity

  Smart Slider 3 Pro for WordPress: Embedded Malicious Code

  CVE-2026-34424Apr 9, 2026Nextendweb
• 8.8 High severity

  Aquasecurity Trivy Embedded Malicious Code Exploited

  CVE-2026-33634Mar 23, 2026AquasecurityEPSS 61.5%
• 9.8 Critical severity

  xygeni-action: Embedded Malicious Code

  CVE-2026-31976Mar 11, 2026Xygeni
• 10.0 Critical severity

  trivy-vscode-extension: Embedded Malicious Code

  CVE-2026-28353Mar 5, 2026Aquasecurity
• 9.8 Critical severity

  ASUS Live Update Embedded Malicious Code Exploited

  CVE-2025-59374Dec 17, 2025ASUSEPSS 1.21%

Spotted an error? Tell us.