→ Back to Home
CI/CD

GitHub Actions Enhances Security by Blocking pull_request_target by Default in Public Repositories

GitHub has announced a significant security update for GitHub Actions, specifically targeting the `pull_request_target` event. Effective December 2, 2026, this trigger will be blocked by default in all public repositories on GitHub Free, Team, and Enterprise Cloud. This change is being rolled out with a brownout period, including one scheduled for today, November 16, 2026, between 16:00–18:00 UTC, during which blocked runs will fail with an error. This update is crucial for open-source maintainers because the `pull_request_target` trigger runs in the context of the base repository and has access to its secrets. This capability, while useful for certain automation scenarios, also presents a significant security risk. Malicious code from a forked repository could potentially exploit this access to compromise the pipeline or steal sensitive credentials, leading to supply chain attacks. By blocking this trigger by default, GitHub is proactively mitigating a common vector for such attacks, forcing maintainers to adopt a more secure posture. This move aligns with the broader industry trend of strengthening software supply chain security. Recent years have seen a surge in attacks targeting CI/CD pipelines and open-source dependencies, making robust security measures a top priority. The shift-left security paradigm, where security considerations are integrated earlier into the development lifecycle, is increasingly becoming standard practice. GitHub's action reflects a commitment to providing a more secure platform for its vast developer community, especially for open-source projects that are often targets due to their public nature and widespread use. In practice, affected practitioners must immediately review their GitHub Actions workflows. Maintainers should check their repository insights to identify any workflows that utilize `pull_request_target` and would be blocked by this new rule. For workflows that legitimately require this trigger, maintainers will need to explicitly allow them through an Actions event policy, ideally using workflow file targeting to grant permissions only to specific, trusted workflows. This requires a careful audit of existing automation to ensure that necessary functionalities continue to operate while adhering to enhanced security standards. Failure to adapt will result in broken CI/CD pipelines for pull requests from forks, hindering contributions and potentially delaying releases.
#github actions#security#ci/cd#open source#supply chain security#devops
Read original source