GitHub actions/checkout Update Blocks Pwn Request Attacks in CI/CD Pipelines

GitHub has announced a critical security update to its official actions/checkout action, effective June 18, 2026, designed to block common pwn request attack patterns that exploit the pull_request_target workflow trigger. The update, which will be backported to all supported major versions by July 16, 2026, aims to strengthen software supply chain security by preventing the checkout and execution of untrusted code from fork pull requests in privileged workflows.

The pull_request_target trigger runs automatically without manual approval when a pull request is opened or updated, operating in the context of the base repository’s default branch with access to secrets and a privileged GITHUB_TOKEN. When combined with actions/checkout to download and execute code from an untrusted fork, attackers can steal tokens and secrets, leading to pwn request attacks. The new version of actions/checkout (v7) refuses to fetch fork pull request code in pull_request_target and workflow_run workflows (when the event is a pull_request* event) unless the workflow author explicitly sets the allow-unsafe-pr-checkout flag to true.

The refusal occurs when the pull request is from a fork and any of the following criteria are met: the repository resolves to the fork’s repository, the ref matches refs/pull/number/head or refs/pull/number/merge, or the ref resolves to a fork pull request’s head or merge commit SHA. This change is aimed at preventing the most common form of pwn requests in the Actions ecosystem.

Recent high-profile attacks that weaponized this behavior include the compromise of multiple packages in the Nx build system (campaign codenamed s1ngularity), as well as breaches of PostHog, TanStack, and the kubernetes-el/kubernetes-el Emacs package. Security firm Socket noted that while this update provides a guardrail, it is not a complete solution, as pwn requests via other event types (e.g., issue_comment) or through other means (git, GitHub CLI) remain out of scope.

Developers are advised to assess the necessity of pull_request_target, switch to pull_request when possible, restrict workflow permissions, and ensure user-controlled input does not lead to untrusted code execution. The update only blocks checkouts of fork pull request head and merge commits, not checkouts of other untrusted repositories.