New GitHub Actions Control Flags Risky Fork Pull Request Workflow Settings
StepSecurity has released a new control designed to identify GitHub organizations and public repositories configured with the least restrictive setting for running fork pull request workflows. This setting, labeled "Approval for running fork pull request workflows from contributors," has three options, with GitHub's default being the middle ground. The new control specifically flags the least restrictive option, which allows any GitHub account with minimal history to execute workflows from a forked repository via a pull request without requiring explicit approval.
This development is crucial for any organization utilizing GitHub Actions, particularly those with public repositories and self-hosted runners. The ability for an attacker to bypass approval and execute arbitrary code on an organization's infrastructure poses a severe supply chain security risk. Such an exploit could lead to unauthorized access to internal networks, credential exfiltration, and broader system compromise. The control helps to proactively identify and remediate a vulnerability that could otherwise be exploited without immediate detection through traditional code review.
This move by StepSecurity aligns with a broader industry trend towards enhancing CI/CD security and supply chain integrity. As CI/CD pipelines become increasingly central to software delivery, they also become prime targets for attackers. GitHub itself has been actively working on hardening the Actions platform, as evidenced by its 2026 security roadmap, which focuses on deterministic dependencies, stronger policy controls, and improved observability. The introduction of workflow-level dependency locking, scoped secrets, and native egress firewalls are all part of this ongoing effort to reduce the attack surface. This new control from StepSecurity complements these platform-level enhancements by providing an external layer of scrutiny for common misconfigurations.
In practice, DevOps and security teams should immediately leverage this new control, or similar auditing mechanisms, to scan their GitHub estate. Organizations should review their "Approval for running fork pull request workflows from contributors" settings for all public repositories, ensuring it is set to at least GitHub's default, or preferably a more restrictive option that requires explicit approval. For those using self-hosted runners, this review is paramount, as the impact of a compromise is significantly higher. Implementing automated checks and integrating security posture management into CI/CD workflows will be essential to prevent such vulnerabilities from being exploited. Practitioners should also stay informed about GitHub's ongoing security roadmap and adopt new features like workflow lockfiles and enhanced secret governance as they become generally available.
Read original source