GitHub tightens security for actions/checkout against supply chain attacks
A new update to GitHub’s popular actions/checkout action is set to roll out on June 18, 2026, aimed at preventing attackers from abusing a common but dangerous workflow trigger to inject and execute malicious code with elevated privileges. The change underscores GitHub’s ongoing efforts to harden its platform against software supply chain risks, particularly those arising from workflows that respond to external pull requests.
Why the pull_request_target trigger is a security concern
The pull_request_target workflow trigger allows workflows to run with the permissions of the repository, even when the pull request comes from a forked repository—an essential feature for many open source projects. However, this convenience has also made it a prime target for attackers. By submitting a specially crafted pull request, an adversary could trick a maintainer into running malicious code within the context of the repository’s workflow, potentially leading to unauthorized access, data exfiltration, or further compromise of the software supply chain.
What’s changing and how it affects developers
Starting next month, the updated actions/checkout will block pwn request attacks by default, preventing workflows triggered by pull_request_target from running if they attempt to check out code using the action. This change affects any workflow that relies on actions/checkout within a pull_request_target context. Affected developers will need to migrate their workflows to actions/checkout@v4 or later and adjust their workflows to avoid using the action directly in pull_request_target triggers. GitHub has indicated that additional guidance and migration tools will be provided to help maintainers update their configurations smoothly.
While the update introduces a necessary security improvement, it also highlights the broader challenge of balancing flexibility and safety in CI/CD pipelines. As software supply chain attacks grow more sophisticated, GitHub’s move reflects a broader industry trend toward tightening security defaults without sacrificing developer productivity.
Source: The Hacker News. AI-assisted editorial synthesis — TechnoExpress.