This website uses cookies to ensure you get the best experience.
Learn more.
A pull_request_target workflow has access to a write-capable token and repository secrets. It checks out the external contributor head commit and executes its install script. What is the central security issue?
Published
- The contributor code becomes trusted automatically because the workflow file came from the base repository.
- A pinned checkout action makes every file downloaded from the pull request safe.
- The risk disappears if the job is renamed pull-request-validation.
- Untrusted pull request code is executing in a privileged workflow context.
Comments — 0
Sign in to comment