Back to Feed
Supply ChainJun 23, 2026

GitHub Updates actions/checkout to Block Common Pwn Request Attack Patterns

GitHub updates actions/checkout to block pwn request attacks via pull_request_target.

GitHub is enhancing supply chain security by updating its 'actions/checkout' tool to block 'pwn request' attacks. These attacks exploit the 'pull_request_target workflow' trigger to run malicious code with elevated privileges. The update, effective June 18, 2026, will refuse to fetch pull request code from forks by default in specific workflow triggers, preventing attackers from stealing secrets and GITHUB_TOKEN.

AI summary of the linked source. Not reviewed by an editor. How this works

Vendor Watch

Run GitHub?

Get an email when a new story names GitHub, usually within the hour.

Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy

The lesson from this incident

Full lesson

The 'pwn request' attack exploits the `pull_request_target` workflow trigger, which runs with elevated repository privileges even when the code originates from an untrusted fork — creating a dangerous trust boundary violation in CI/CD pipelines. Attackers can leverage this to execute arbitrary code with access to repository secrets and the GITHUB_TOKEN, effectively compromising the entire software supply chain. This matters because CI/CD pipelines have become high-value targets: a single compromised workflow can lead to secret exfiltration, malicious code injection into builds, or full repository takeover. GitHub's June 2026 update enforces safer defaults, but organizations relying on custom workflows must audit their own configurations proactively rather than waiting for the deadline.

What helps against this

How we list vendors

Entities

actions/checkout (product)GitHub (vendor)s1ngularity (campaign)Nx build system (product)PostHog (product)TanStack (product)