Repository navigation
Pin upstream pr-agent image by digest - #3
Merged
Merged
Conversation
The action ran FROM codiumai/pr-agent:github_action, a mutable tag, so a compromised upstream push (cf. the LiteLLM 1.107.0 supply-chain attack) would run immediately in every repo that uses this action with OPENAI_KEY and a write-scoped GITHUB_TOKEN. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Why
Dockerfile.github_action_dockerhubranFROM codiumai/pr-agent:github_action, a mutable upstream tag. Every repo that callssofatutor/pr-agent@mainruns that image withOPENAI_KEYand a write-scopedGITHUB_TOKEN, so a compromised upstream push would execute immediately across the org. pr-agent bundles litellm, which shipped a malicious 1.107.0 this week (The Hacker News).What
Pin the image to its current digest,
sha256:960571f0…. Docker Hub shows the tag was last updated on 2026-04-16, before 1.107.0 was published, so behaviour is unchanged.The caller repos are being pinned to this PR's head commit
b9f94cea4334bffee2d8429eb21d742114198cca. A squash or rebase merge followed by deleting the branch would eventually leave that SHA unreachable and break the action.Related: the
sofatutor-kidsbranch gets the same fix in a separate PR, and Dependabot with a 7-day cooldown is in another.🤖 Generated with Claude Code