Skip to content

chore(stack): pin mailpit to v1.30.2 - #6748

Closed
supabase-cli-releaser[bot] wants to merge 1 commit into
developfrom
sync/stack-workload-catalog-mailpit
Closed

supabase-cli-releaser[bot] wants to merge 1 commit into
developfrom
sync/stack-workload-catalog-mailpit

Conversation

@supabase-cli-releaser

Copy link
Copy Markdown
Contributor

Pins packages/stack/src/Artifacts.ts to the
mailpit v1.30.2
slim-services release and its image digest.

Opened from the mirror-slim-image dispatch. artifactFor derives the
native release tag, asset names, and URLs from service + version, so this
pin is the whole change.

@supabase-cli-releaser
supabase-cli-releaser Bot requested a review from a team as a code owner September 23, 2026 14:58
mail: definition(
"mailpit",
"v1.30.2",
"ghcr.io/supabase/cli/mailpit:v1.30.2@sha256:37a38e48e9338cd7e89dfeb487f37b02ebfcd9cb23111bed2d345e79d37d6dd6",

Copy link
Copy Markdown

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/events to the default unauthenticated Mailpit endpoint; routing reaches /api/events while origin validation is skipped, streaming captured email metadata and body snippets, including password-reset tokens, cross-origin. GHSA-8r62-w5wh-fc5m
Helpful? 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 current v1.30.2 version and digest with the values from v1.30.6 (or the latest patched release >= v1.30.6).

@avallete avallete closed this Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants