GitHub Actions holds potentially malicious workflows for approval
GitHub Actions now holds certain workflow runs for approval to protect public repositories from supply chain attacks. This feature automatically prevents malicious workflows from executing until a collaborator with write access reviews and approves them via an authenticated web session. This protection is applied automatically and currently only affects public repositories on github.com, not GitHub Enterprise Server.
- →Hold potentially malicious GitHub Actions workflows for manual approval
- →Protection applies only to public repositories on GitHub.com
Security (1) ›
- Hold potentially malicious GitHub Actions workflows for manual approval
GitHub Actions now automatically holds potentially malicious workflow runs for approval to mitigate supply chain attacks. A repository collaborator with write access must review and approve the workflow before it executes.
Notes (1) ›
- Protection applies only to public repositories on GitHub.com
This new security protection is automatically enabled for public repositories on github.com. GitHub Enterprise Server does not currently include this protection.
https://github.blog/changelog/2026-07-28-github-actions-holds-unproven-workflows-for-approval
Related releases
- GitHub Copilot Enterprise Teams Model Policy Targeting in Public Preview GitHub Changelog ·
- npm restricts granular access token ability to bypass 2FA for sensitive actions GitHub Changelog ·
- GitHub Models officially retired GitHub Changelog ·
- GitHub Copilot VS Code Updates: Agents, Chat, UI, and Accessibility GitHub Changelog ·
- GitHub Actions: Reference same-repo workflows with self-repository syntax GitHub Changelog ·
- GitHub Stacked Pull Requests Enter Public Preview GitHub Changelog ·