Skip to content

fix(auth): Verify primary email on password reset#115651

Merged
michelletran-sentry merged 1 commit into
masterfrom
fix/verify-email-on-password-reset
May 15, 2026
Merged

fix(auth): Verify primary email on password reset#115651
michelletran-sentry merged 1 commit into
masterfrom
fix/verify-email-on-password-reset

Conversation

@michelletran-sentry
Copy link
Copy Markdown
Contributor

Completing a password reset proves the user controls the inbox the reset link was sent to. Move the verify_user_email call out of the relocate-only block so it runs for all recovery modes, matching the reasoning already documented for the relocation flow.

I've confirmed that the one potential exploit is not actually exploitable (user changes their primary email to another email before password reset completes, which verifies that other email instead of the one they sent). However, you can't promote an unverified email to primary, so we're safe.

Completing a password reset proves the user controls the inbox the
reset link was sent to. Move the verify_user_email call out of the
relocate-only block so it runs for all recovery modes, matching the
reasoning already documented for the relocation flow.

Co-Authored-By: Claude <noreply@anthropic.com>
@michelletran-sentry michelletran-sentry requested a review from a team as a code owner May 15, 2026 17:27
@github-actions github-actions Bot added the Scope: Backend Automatically applied to PRs that change backend components label May 15, 2026
@michelletran-sentry michelletran-sentry requested a review from a team May 15, 2026 17:28
@michelletran-sentry michelletran-sentry merged commit 1018aae into master May 15, 2026
63 checks passed
@michelletran-sentry michelletran-sentry deleted the fix/verify-email-on-password-reset branch May 15, 2026 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Backend Automatically applied to PRs that change backend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants