TL;DR: On June 24, 2026, Novee Security disclosed Cordyceps, a class of exploitable CI/CD workflow weaknesses that let an anonymous attacker hijack pull-request pipelines, steal secrets, and push code on behalf of trusted repositories. Novee scanned roughly 30,000 high-impact repos and confirmed more than 300 were fully exploitable, including projects at Microsoft, Google, Apache, Cloudflare, and the Python Software Foundation. North Carolina small businesses that use GitHub Actions or any CI/CD pipeline, whether for custom software, integrations, or even Markdown docs, need to harden pull-request workflows now.
Key takeaway: If you run GitHub Actions on pull requests, an unauthenticated stranger with a free GitHub account can be a privileged user in your build. Cordyceps is the wake-up call.
Need help hardening your CI/CD pipelines and vendor due diligence? Contact Preferred Data Corporation for a Software Supply Chain Review. Local, BBB A+ since 1987. Call (336) 886-3282.
What is the Cordyceps CI/CD vulnerability?
Cordyceps is a class of CI/CD workflow weaknesses, disclosed by Novee Security on June 24, 2026, that lets attackers use malicious pull requests to compromise the build pipelines that produce, sign, and publish software. Novee's research describes a systemic pattern across the open-source ecosystem: command injection, broken authentication logic, artifact poisoning chains, and privilege escalation rooted in mis-scoped GitHub Actions workflows.
Novee's team scanned roughly 30,000 high-impact repositories, validated hundreds of fully exploitable chains, and worked with maintainers at Microsoft, Google, Apache, Cloudflare, and the Python Software Foundation to ship fixes. In a single scan, 654 repositories were flagged and more than 300 were confirmed fully exploitable, meaning an attacker could execute code on the project's CI infrastructure, steal credentials, or directly compromise the supply chain.
For background, see Novee's disclosure, The Hacker News, Dark Reading, SecurityWeek, and Cybersecurity News.
Why does a CI/CD bug matter for a North Carolina small business?
A CI/CD bug matters because most North Carolina small businesses already depend on someone's CI/CD pipeline, even if they have never written a line of code. Your bookkeeping integration, your ERP plug-in, your factory data dashboard, the npm packages inside your e-commerce site, all of them ship through automated build pipelines that, if hijacked, can deliver tampered code straight into your business.
There are three SMB scenarios that map directly to Cordyceps risk:
- You build custom software or have an in-house developer. A
pull_request_targetworkflow that runs untrusted code with privileged secrets can leak your AWS keys, Stripe tokens, or signing keys to anyone with a GitHub account. - You use open-source software you do not maintain. A poisoned release of a popular package can deliver malicious code into your production builds via your normal dependency updates.
- You buy SaaS that is built on open-source CI/CD. Your vendor's CI/CD pipeline becomes your CI/CD pipeline; if they get compromised, the next "routine update" might not be routine.
Small businesses without dedicated security staff are precisely the segment that ships open-source updates the day they land. That is exactly the threat model Cordyceps exploits.
Key takeaway: Treat CI/CD like production: who can run code in there, what secrets does it see, and how would you know if a stranger had been there.
Want a vendor and pipeline risk assessment? Explore Preferred Data Cybersecurity services or call (336) 886-3282.
What does a Cordyceps-style attack actually look like?
A Cordyceps-style attack looks like a routine open-source pull request that quietly redirects the project's automated build into the attacker's hands. The attacker does not need to "break in" in the traditional sense; they exploit the trust the build pipeline already extends to incoming code.
The mechanics matter because they shape the fix:
| Attack stage | What the attacker does | What it costs a victim |
|---|---|---|
| Bait | Open a PR (or a comment on a PR) that triggers a workflow | Free GitHub account |
| Privilege abuse | Workflow runs with secrets and write tokens it should not have | CI runner controlled |
| Secret theft | Read environment variables, GitHub App keys, cloud tokens | Long-lived credentials leaked |
| Artifact poisoning | Modify build outputs, container images, or release tags | Downstream users shipped malware |
| Persistence | Push to protected branches via stolen tokens | Quiet, long-term access |
The published Microsoft Azure Sentinel example is the cleanest illustration: a comment on a pull request triggered code execution on Microsoft's CI infrastructure and exfiltrated a non-expiring GitHub App key. Replace "Microsoft" with "your ERP integration vendor" and the consequence is the same.
How should a North Carolina SMB harden its CI/CD pipelines?
A North Carolina SMB should harden CI/CD pipelines by treating them as production systems with least privilege, secret hygiene, and review gates, not just convenient automation. The fixes are concrete, repeatable, and largely free.
A practical 10-point checklist for your team or your IT partner:
- Audit every workflow that triggers on pull requests. Replace
pull_request_targetwithpull_requestunless you have a specific, documented reason. Default to running PR code with NO secrets. - Enforce least-privilege tokens. Set
permissions:at the workflow and job level. Default topermissions: read-all, opt in to writes only where required. - Require approval for fork PRs. Enable "Require approval for first-time contributors" or stricter on every public repo.
- Pin actions to a full SHA, not a tag.
uses: actions/checkout@v4is mutable; pin to a SHA so a hijacked tag cannot run new code. - Use OIDC for cloud credentials. Replace long-lived AWS/Azure/GCP keys in GitHub secrets with short-lived OIDC tokens that expire in minutes.
- Rotate any secret a PR workflow has ever touched. Assume any secret available to a PR workflow has been seen.
- Block scripts that read all environment variables. Add CodeQL or SAST to your workflows to flag wholesale env dumping.
- Branch protection on default branches. Require PR review, status checks, and signed commits.
- Generate and review SBOMs (Software Bill of Materials). A simple
actions/dependency-review-actionstep on PRs catches risky dependency adds. - Log and alert on workflow changes. A change to
.github/workflows/*.ymlshould kick a notification to security or the IT partner, not silently merge.
That list is short, but in our experience it shuts down 90% of the failure modes Cordyceps describes. The 10% that remains is where having a partner who reviews vendor risk and pipeline configuration earns its keep.
Want this audited on your real repositories? Schedule a Software Supply Chain Review or call (336) 886-3282.
What about SMBs that do not build software themselves?
SMBs that do not build software themselves still inherit CI/CD risk from every vendor and every open-source dependency in their stack, which makes vendor due diligence the most important Cordyceps response for non-developers. You cannot patch a vendor's pipeline, but you can refuse to trust one that will not answer basic questions.
Practical vendor questions to send to every software vendor in 2026:
- Do you publish a Software Bill of Materials (SBOM) or align with SLSA or NIST SSDF?
- How do you protect signing keys and GitHub App credentials in your CI/CD?
- What is your process for handling malicious pull requests on open-source dependencies you ship?
- When you patch a Cordyceps-class issue, how will you notify customers?
- Do you require MFA on every developer account with commit rights?
A vendor that cannot answer those is a vendor whose updates you should not auto-apply. North Carolina manufacturers running plant-floor software, accounting firms running cloud bookkeeping, and law firms running document automation all carry this exposure today.
What should NC manufacturers and professional firms do this week?
NC manufacturers and professional firms should do four things this week: inventory who pushes code to your repos and pipelines, freeze any PR-triggered workflows that handle secrets, send the vendor question list above to your top five software vendors, and book a CI/CD review for repos that touch money, customer data, or production systems.
Industry-specific priorities:
- Manufacturing. Plant floor MES, SCADA front-ends, and any custom dashboards or integrations are often quietly maintained in a single repo with broad workflow permissions. Tighten those first. Pair with OT/IT integration to keep IT-side compromises out of OT networks.
- Professional services (legal, accounting, financial). Bookkeeping plug-ins, document automation, and client portals frequently rely on small SaaS vendors. Add software supply chain questions to your annual vendor risk review.
- Defense-adjacent firms. SLSA-aligned build provenance is increasingly expected in CMMC audits and DoD subcontracts. Cordyceps is the perfect prompt to align early.
A national reseller selling a shrink-wrapped CI/CD tool cannot tell you which of YOUR specific workflows are exposed. A local, manufacturing-savvy partner can.
Frequently Asked Questions
Is Cordyceps a single CVE I can patch?
No. Cordyceps describes a class of misconfigurations and unsafe patterns across CI/CD systems, primarily GitHub Actions, rather than a single bug in one product. The fix is workflow hygiene and least-privilege configuration in your own repositories, plus vendor pressure on the projects you depend on.
My business has zero developers. Am I still exposed?
Yes, but indirectly. Any SaaS you use is built and shipped through a CI/CD pipeline; if that pipeline is hijacked, the next routine update can deliver malicious code. The right response is vendor due diligence and a layered defense (EDR, MFA, network segmentation) so a single bad update does not turn into a full breach. Talk to a managed IT partner about the gaps.
How much does hardening our GitHub Actions cost?
Most of the work is free, it is configuration changes and policy. The cost is the engineering or partner time to do the audit, write the playbook, and train developers. For a typical NC SMB with a small repo footprint, a Software Supply Chain Review usually pays for itself the first time it prevents a routine update from going sideways. Call (336) 886-3282 for a tailored estimate.
Will my cyber insurance cover a CI/CD breach?
Maybe, but increasingly only if you can document basic controls (MFA, EDR, secret rotation, vendor due diligence). Cyber insurers are tightening underwriting around software supply chain risk; lacking documentation of CI/CD controls is fast becoming a denied claim. Preferred Data helps NC businesses produce the documentation insurers want before they ask.
Is this just an open-source problem?
No. The same patterns appear in private repos. Most SMBs have at least one PR-triggered workflow that runs untrusted code with too much access, often inherited from a copy-pasted template. Private repos hide the problem; they do not solve it.
How is Preferred Data different from a national managed security provider?
Preferred Data is a High Point, NC company founded in 1987 with 37+ years of IT experience and a 20+ year average client tenure. We pair CI/CD and software supply chain reviews with the managed IT, cybersecurity, and custom software work that makes the fixes stick in a real business. Local, on-site, and accountable.