CTIPilot

Cordyceps

campaign · campaign:cordyceps-github-actions-pwn-request

GitHub Actions pull_request_target 'pwn request' vulnerability class.

Coverage timeline
1
first 2026-06-25 → last 2026-06-25
Peak priority
high
1 high
Sources cited
3
3 hosts
Sections touched
1
research
Co-occurring entities
0
no co-occurrence
ATT&CK techniques
1
pinned v19.2 · see below

ATT&CK techniques

1 technique observed across 1 entry, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v19.2 · compare on the matrix · Navigator layer (JSON)

Initial Access TA0001

T1195.002Supply Chain Compromise: Compromise Software Supply Chain×1

Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise. Supply chain compromise of software can take place in a number of ways, including manipulation of the application source code, manipulation of the update/distribution mechanism for that software, or replacing compiled releases with a modified version.

Evidence: 2026-06-25/cordyceps-the-github-actions-pull-request-target-pwn-request · ATT&CK page ↗

Story timeline

  1. 2026-06-25"Cordyceps"; the GitHub Actions pull_request_target pwn-request class is still widely exploitable at scale
    research

Where this entity is cited

  • research1

Source distribution

  • github.blog1 (33%)
  • novee.security1 (33%)
  • securityweek.com1 (33%)

explore in graph

Entries about Cordyceps (1)

2026-06-25 · view entry permalink →

HIGH

"Cordyceps"; the GitHub Actions pull_request_target pwn-request class is still widely exploitable at scale

Novee Security published "Cordyceps", an empirical study of a long-known but persistently unmitigated class of GitHub Actions CI/CD vulnerabilities (Novee Security, 2026-06-23 · SecurityWeek, 2026-06-24). The pattern: a pull_request_target (or comment-triggered) workflow runs with the base repository's write permissions and secrets while checking out or otherwise consuming untrusted fork-PR content, letting an attacker inject code into a privileged CI context (T1195.002). Of ~30,000 high-impact repositories scanned, 654 were flagged and 300+ confirmed fully exploitable, including Microsoft (Azure Sentinel), Google (AI Agent Development Kit), Apache (Doris), Cloudflare (Workers SDK) and the Python Software Foundation (Black), with exploitation requiring only a free GitHub account and a single PR. Successful exploitation can yield the org's GitHub App key, cloud repository authority, or the ability to publish attacker-controlled packages to trusted registries. GitHub shipped actions/checkout v7 on 18 June with safer pull_request_target defaults that refuse to fetch fork-PR head commits in unsafe patterns (GitHub Changelog, 2026-06-18), but organisations pinning older action versions or running self-managed Enterprise Server are not yet protected. Audit .github/workflows/*.yml for pull_request_target triggers that reference any ${{ github.event.pull_request.* }} context in run:/env: steps; scope GITHUB_TOKEN to contents: read by default; and split build/test onto the unprivileged pull_request trigger.

Scans of 30,000 high-impact repositories flagged 654 vulnerable instances; over 300 were confirmed fully exploitable

Novee Security

GitHub updated actions/checkout on June 18 to block common pwn-request patterns

GitHub Changelog
research25 Jun 04:59Zmulti-sourceOpen finding ↗