mediumPublished September 1, 2025

Supabase Advisory · Leaked-Password Protection Off by Default

Summary

Supabase Auth's integration with HaveIBeenPwned · which rejects passwords found in known breaches · is disabled by default on every new project. Combined with the ~700M compromised passwords in circulation, this leaves signups vulnerable to trivial credential stuffing. This is a configuration advisory rather than a CVE, but the exposure is systemic.

Affected

  • Every Supabase project created without explicitly enabling leaked-password protection
  • Applies to email/password signup flows · not OAuth-only projects

Impact

Users can sign up with passwords like `password123` or previously-breached credentials tied to their email. Credential-stuffing tools automate account takeover against any exposed login endpoint. Impact scales with user base and whether the app holds sensitive data.

How to Fix

  1. 1Supabase Dashboard > Authentication > Providers > Email · toggle 'Leaked password protection' on.
  2. 2Set a minimum password length of 12+ characters in the same panel.
  3. 3Enable rate limits on signup and login endpoints (on by default; verify).
  4. 4Offer TOTP MFA for accounts with real value (payments, admin, private data).

Check If Your App Is Affected

Free 30-second scan · we look for this issue and 50 more.

Scan Now

Other Advisories