Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Severity: MEDIUM
The newly pinned imgproxy v3.26.0 is affected by CVE-2025-24354/GHSA-j2hp-6m75-v4j4 (all versions <3.27.2). An attacker controlling an image-source URL sent through Storage/imgproxy can request
0.0.0.0; imgproxy may then reach local services and disclose their responses. GHSA-j2hp-6m75-v4j4Helpful? Add 👍 / 👎
💡 Fix Suggestion
Suggestion: Upgrade imgproxy from v3.26.0 to v3.27.2 or later to fix CVE-2025-24354 (SSRF). This requires two coordinated changes: (1) on line 101, change the version string from
"v3.26.0"to"v3.27.2"; (2) on line 102, update the image reference to"ghcr.io/supabase/cli/imgproxy:v3.27.2@sha256:<new-digest>", replacing<new-digest>with the actual SHA-256 digest of the v3.27.2 image pulled fromghcr.io/supabase/cli/imgproxy:v3.27.2.