CVE-2026-45321
CRITICALCISA KEVEPSS 82th pctlDescription
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.
How to fix
Actively exploited, no published fix found yet
Federal remediation due: 2026-06-10
Known ransomware campaign use
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Exploit Intelligence
Elevated risk: more likely to be exploited than 82% of all known CVEs.
Remediation due: 2026-06-10
Associated with ransomware campaigns
References
Related Vulnerabilities
Other CWE-506 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-3094 | Critical | 10.0 | 86% | - | Fix |
| CVE-2025-30066 | High | 8.6 | 72% | KEV | - |
| CVE-2026-33634 | High | 8.8 | 59% | KEV | Fix |
| CVE-2024-4978 | High | 8.4 | 27% | KEV | - |
| CVE-2025-54313 | High | 7.5 | 4.1% | KEV | Fix |
| CVE-2025-30154 | High | 8.6 | 2.3% | KEV | Fix |
Common questions
How do I fix CVE-2026-45321?
No published fix for CVE-2026-45321 has been found yet. It is on the CISA Known Exploited Vulnerabilities list; federal agencies must remediate by 2026-06-10. Apply the vendor's mitigations per CISA's guidance.
Is CVE-2026-45321 being actively exploited?
Yes. CVE-2026-45321 is listed in the CISA Known Exploited Vulnerabilities catalog, which means exploitation has been observed in the wild. CISA has also linked it to known ransomware campaigns. US federal agencies were required to remediate it by 2026-06-10. Treat it as a priority whatever its CVSS score says.
How severe is CVE-2026-45321?
CVE-2026-45321 has a CVSS v3 base score of 9.6, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-45321
Markdown
[](https://tridentstack.com/cve/CVE-2026-45321)HTML
<a href="https://tridentstack.com/cve/CVE-2026-45321"><img src="https://tridentstack.com/cve/badge/CVE-2026-45321.svg" alt="CVE-2026-45321"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-29.