https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 12:11:06 +0000 https://cve.radiocsirt.org/vuln/cve-2026-45321 <p><strong>Affected:</strong> @tanstack arktype-adapter, @tanstack eslint-plugin-router, @tanstack eslint-plugin-start, @tanstack history, @tanstack nitro-v2-vite-plugin, @tanstack react-router, @tanstack react-router-devtools, @tanstack react-router-ssr-query, @tanstack react-start, @tanstack react-start-client and 32 more</p> <p>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 &#34;Pwn Request&#34; 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.</p> <p><strong>Affected:</strong> @tanstack arktype-adapter, @tanstack eslint-plugin-router, @tanstack eslint-plugin-start, @tanstack history, @tanstack nitro-v2-vite-plugin, @tanstack react-router, @tanstack react-router-devtools, @tanstack react-router-ssr-query, @tanstack react-start, @tanstack react-start-client and 32 more</p> <p>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 &#34;Pwn Request&#34; 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.</p> https://cve.radiocsirt.org/vuln/cve-2026-45321