GitHub Actions to block pull_request_target by default
Public repositories lose the risky trigger on Dec. 2 unless an Actions policy allows it, and GitHub has opened its impact reports to every plan.

In short
- 01GitHub Actions will block pull_request_target in public repos starting Dec. 2 unless an Actions event policy allows it.
- 02GitHub's rule covers Free, Team and Enterprise Cloud, while private repos, internal repos and GitHub Enterprise Server aren't affected.
- 03GitHub opened policy Insights and evaluate mode to every plan after an open source maintainer asked how smaller projects could see what would break.
The story
GitHub just opened its impact reports to every plan, ahead of the Dec. 2 change that blocks the pull_request_target trigger in public repos. After that, those workflows won't run unless an Actions event policy allows them.
Enforcement was first planned for a month earlier. Socket's report on the change ties this kind of attack, known as a pwn request, to supply chain incidents at Nx, PostHog and TanStack.
The trigger can hand fork code a repository's secrets
The trigger runs in the context of the base repo and can read its secrets. That's handy for labeling pull requests or posting comments. But if a workflow also runs code from a fork, that code could steal those secrets or poison the pipeline.
Socket notes that the new default goes further than an earlier fix to actions/checkout, which rejected common unsafe fork checkouts. This one stops the event itself, even for workflows that use it safely. InfoQ's report on Actions lockfiles lists it among the defaults GitHub is tightening.
Every plan can now see which workflows would break
Until the deadline, the rule runs in evaluate mode. Workflows keep running with a warning, and Insights shows which ones would be blocked. GitHub also scheduled two two-hour brownouts this month, when blocked runs would fail with an error.
At first, that report was limited to Enterprise customers. In a GitHub Community discussion, maintainer George Joseph asked how "us mere mortals who run open-source organizations" could see what would be affected. A GitHub employee later posted the answer.
Viewing insights, along with evaluate mode for all plan types have shipped.
Steve-Glass of GitHub, in the GitHub Community discussion
Maintainers have two ways to keep workflows running
GitHub's security docs suggest moving a workflow to the safer pull_request event if it doesn't need the extra access. If it does, admins can add an event policy that allows the trigger for specific workflow files.
The change covers public repos on GitHub Free, Team and Enterprise Cloud. Private and internal repos and GitHub Enterprise Server aren't affected, and existing event policies stay in place.
Why it matters
GitHub is trading convenience for a safer default, and careful maintainers pay part of the bill. A workflow that only labels pull requests now needs an allow rule or it stops running. Given how often pwn requests have fed real supply chain attacks, that's a fair trade, but public repos should check Insights now.
Share


