Add least-privilege permissions to triage workflow#1576
Merged
Conversation
Add explicit permissions: block (pull-requests: write, issues: write) to constrain GITHUB_TOKEN scope on pull_request_target trigger. Ref: https://www.stepsecurity.io/blog/hackerbot-claw-github-actions-exploitation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
github-actions
bot
added
the
needs triage
dopey
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
permissions:block (pull-requests: write,issues: write) to the triage workflow that triggers onpull_request_target, constraining theGITHUB_TOKENto only the scopes actually neededRef: StepSecurity hackerbot-claw analysis
Test plan
🤖 Generated with Claude Code