返回首页
Socket Blog··论文与技术

GitHub to Block pull_request_target Workflows by Default Starting December 2

中文摘要

为防止 CI/CD 漏洞和凭据窃取,GitHub 将于 2026 年 12 月 2 日起,默认禁止公共仓库使用 pull_request_target 工作流。

English Summary

Starting December 2, 2026, GitHub will block pull_request_target workflows by default in public repositories to prevent CI/CD vulnerabilities and credential theft.

原文节选

GitHub will begin blocking GitHub Actions workflows triggered by pull_request_target in public repositories on December 2, 2026, expanding its protections against a class of CI/CD vulnerabilities that has repeatedly enabled attackers to steal credentials and compromise open source software releases. The restriction, originally announced in September, will prevent affected workflows from running unless an applicable Actions event policy explicitly allows them. GitHub had initially scheduled enforcement for November 2 but confirmed the postponed December 2 deadline in a new update this week, giving maintainers additional time to review their automation and configure exceptions. The new restriction goes beyond protections introduced in June, when GitHub updated actions/checkout to prevent common attempts to check out untrusted pull request code inside privileged workflows. This time, GitHub is blocking the pull_request_target trigger itself by default, including for workflows that use it safely. pull_request_target Is Now a Common Attack Vector Vector # GitHub introduced pull_request_target in 2020 to help maintainers automate tasks involving pull requests from external contributors. …