GitHub Actions holds workflows for approval to prevent attacks
GitHub Actions now automatically holds potentially malicious workflows for approval before execution to prevent supply chain attacks. This measure requires a repository collaborator with write access to review and approve the workflow run through an authenticated web session. This protection is active for public repositories on GitHub.com and is not configurable by users. GitHub Enterprise Server is not affected by this change.
- →GitHub Actions holds workflows for approval to prevent supply chain attacks
- →Approval process and scope
Security (1) ›
- GitHub Actions holds workflows for approval to prevent supply chain attacks
GitHub Actions now holds certain workflow runs for approval before they start to protect public repositories from malicious workflows that steal CI/CD credentials. Workflow runs identified as potentially malicious will not execute until a repository collaborator with write access reviews and approves them. This protection is automatically applied to public repositories on GitHub.com and does not require user configuration.
Notes (1) ›
- Approval process and scope
The approval must be submitted through an authenticated web session, after which the workflow continues normally. This protection currently applies only to public repositories on github.com, and GitHub Enterprise Server does not include this feature at this time.
https://github.blog/changelog/2026-07-28-github-actions-holds-potentially-malicious-workflows-for-approval
Related releases
- CodeQL 2.26.1 enhances analysis accuracy and framework coverage GitHub Changelog ·
- GitHub Copilot App Usage Metrics Expanded in API GitHub Changelog ·
- npm Adds Publish-Time Malware Scanning and Dual-Use Metadata GitHub Changelog ·
- Grok 4.5 reasoning model available in GitHub Copilot GitHub Changelog ·
- Dependabot alerts expand to cover malicious packages from OpenSSF GitHub Changelog ·
- GitHub Actions holds potentially malicious workflows for approval GitHub Changelog ·