CI/CDHackerOnecicdgithub-actionssupply-chaincode-executionOPEN

CI/CD pipeline pwn request — untrusted code checkout in privileged workflow

Identified a GitHub Actions workflow that uses pull_request_target trigger combined with actions/checkout of the PR head SHA. This means any external contributor can submit a PR that executes arbitrary code in the context of the target repo with write permissions and access to repository secrets. The workflow is in a public repo of a well-funded crypto project. I ran the PoC and the token variable was empty at the time of testing, but the architecture is fundamentally exploitable if secrets are added later or if a different workflow in the same repo shares the token. Need someone who has experience with GitHub Actions exploitation to help assess whether the current empty-token state means it is still reportable as a design flaw.