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 pinned Mailpit v1.30.2 image is affected by GHSA-8r62-w5wh-fc5m. A malicious website can send
/%61pi/eventsto the default unauthenticated Mailpit endpoint; routing reaches/api/eventswhile origin validation is skipped, streaming captured email metadata and body snippets, including password-reset tokens, cross-origin. GHSA-8r62-w5wh-fc5mHelpful? Add 👍 / 👎
💡 Fix Suggestion
Suggestion: Upgrade the pinned Mailpit image from v1.30.2 to v1.30.6 or later, which patches GHSA-8r62-w5wh-fc5m. Update both the version string (line 125) and the image URI with the new tag and its corresponding SHA256 digest (line 126). You can retrieve the correct digest for the patched image by running:
docker pull ghcr.io/supabase/cli/mailpit:v1.30.6 && docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/supabase/cli/mailpit:v1.30.6. Replace the currentv1.30.2version and digest with the values from v1.30.6 (or the latest patched release >= v1.30.6).