Novee says insecure CI/CD workflows in widely used open-source repositories could let unauthenticated attackers take over projects and poison downstream software releases. The researchers call the issue class "Cordyceps" and say vulnerable GitHub Actions YAML workflows let untrusted pull requests or comments trigger low-privilege jobs that flow into high-privilege jobs, enabling command injection, forged approvals, malicious code pushes, artifact poisoning, and cloud credential theft. Confirmed affected repositories include projects from Microsoft, Google, Apache, Cloudflare, and the Python Software Foundation.
Why it matters: This matters because one weak workflow in a popular project can spread malicious code or stolen credentials far beyond the original repository, affecting developers, companies, and end users. Maintainers should urgently review GitHub Actions and other CI/CD workflows for unsafe trust boundaries, especially where pull requests, comments, signing keys, cloud credentials, or release publishing are involved.
Ionut Arghire
2026.06.24
100% relevant
This article establishes a distinct new story about a newly named class of CI/CD workflow vulnerabilities affecting major open-source repositories and the broader software supply chain, not a follow-up to a previously tracked incident.
← Back to all stories