Repository navigation
chore(stack): pin mailpit to v1.30.2 - #6734
supabase-cli-releaser[bot] wants to merge 1 commit into
Conversation
| mail: definition( | ||
| "mailpit", | ||
| "v1.30.2", | ||
| "ghcr.io/supabase/cli/mailpit:v1.30.2@sha256:37a38e48e9338cd7e89dfeb487f37b02ebfcd9cb23111bed2d345e79d37d6dd6", |
There was a problem hiding this comment.
🟡 Severity: MEDIUM
Mailpit v1.30.2 in this newly immutable digest is affected by GHSA-8r62-w5wh-fc5m. A malicious website can request /%61pi/events on a local unauthenticated Mailpit instance, bypass origin validation, and receive stored emails—including password-reset tokens—over the WebSocket.
Helpful? Add 👍 / 👎
💡 Fix Suggestion
Suggestion: Upgrade Mailpit from v1.30.2 to v1.30.6 (or later) to resolve the CSRF/WebSocket origin-validation bypass described in GHSA-8r62-w5wh-fc5m. The recommended approach is to re-trigger the mirror-slim-image workflow dispatch targeting Mailpit v1.30.6, which will automatically compute the correct image digest and open a new pin PR. Alternatively, update manually: (1) change line 125 from "v1.30.2" to "v1.30.6", and (2) change line 126 to "ghcr.io/supabase/cli/mailpit:v1.30.6@sha256:<correct-digest-for-v1.30.6>", where the digest is obtained by pulling ghcr.io/supabase/cli/mailpit:v1.30.6 and inspecting its manifest digest via docker inspect --format='{{index .RepoDigests 0}}' ghcr.io/supabase/cli/mailpit:v1.30.6 or the GHCR API.
Pins
packages/stack/src/Artifacts.tsto themailpitv1.30.2slim-services release and its image digest.
Opened from the
mirror-slim-imagedispatch.artifactForderives thenative release tag, asset names, and URLs from service + version, so this
pin is the whole change.