github.blog
What's coming to our GitHub Actions 2026 security roadmap
The playbook is consistent: - Vulnerabilities allow untrusted code execution - Malicious workflows run without observability or control - Compromised dependencies spread across thousands of repositories - Over-permissioned credentials get exfiltrated via unrestricted network access Today, too many of these vulnerabilities are easy to introduce and hard to detect. We’re working to address this gap. … ... The current challenge Action dependencies are not deterministic and are resolved at runtime. Workflows can reference a dependency by various mutable references including tags and branches. … **2. Reducing attack surface with secure defaults** **The current challenge** GitHub Actions is flexible by design. Workflows can run: - In response to many events - Triggered by various actors - With varying permissions But as organizations scale, the relationship between repository access and workflow execution needs more granularity. Different workflows, teams, and enterprises need very different levels of exposure. Moreover, it leads to over-permissioned workflows, unclear trust boundaries, and configurations that are easy to get wrong. … - Who can trigger workflows - Which events are allowed This shifts the model from distributed, per-workflow configuration that’s difficult to audit and easy to misconfigure, to centralized policy that makes broad protections and restrictions visible and enforceable in one place. **Our core policy dimensions include:** - **Actor rules** specify*who* can trigger workflows such as individual users, roles like repository admins, or trusted automation like GitHub Apps, GitHub Copilot, or Dependabot. - **Event rules** define*which* GitHub Actions events are permitted like push, pull_request, workflow_dispatch, and others. … ## Scoped secrets and improved secret governance ### The current challenge Secrets in GitHub Actions are currently scoped at the repository or organization level. This makes secrets difficult to use safely, particularly with reusable workflows where credentials flow broadly by default. Teams need finer-grained controls to bind credentials to specific execution contexts.
Related Pain Points2件
GitHub Actions lacks lockfile dependency management
9GitHub Actions has no lockfile system to pin exact versions of third-party actions. Every workflow run re-resolves dependencies from the manifest without recording what was actually chosen, creating non-deterministic builds and enabling supply chain attacks. This is a fundamental gap compared to mature package managers.
Over-privileged GitHub Actions workflows
899.8% of GitHub Actions workflows are over-privileged, meaning repositories grant excessive permissions that increase vulnerability to attacks. Secrets are scoped at repository or organization level, flowing broadly by default in reusable workflows without fine-grained controls to bind credentials to specific execution contexts.