Supabase "Leaked Password Protection Disabled": what it means and how to fix it
Short answer: Supabase's Security Advisor shows Leaked Password Protection Disabled when leaked password protection is off, so Supabase Auth can accept passwords that already appear in data breaches if they meet your other password rules. Open Authentication, then Sign In / Providers, then Email, turn on the option to prevent leaked passwords and save. Supabase says this is available on the Pro Plan and above; on Free, set a minimum length of 8 or more and require mixed characters. SniffPup, a free passive security scanner for vibe-coded apps, can then run a free SniffPup scan of your own site to see what visitors can reach.
Passive, read-only checks only, for a live URL you own or are authorized to test. The free scan does not read your Supabase Auth settings; this is not a source, RLS, or security audit. A score of 100 means no issues were found in our checks, not proof of security. Full fixes free for every critical issue (no critical? one other fix is free).
Home › Guides › Supabase "Leaked Password Protection Disabled": what it means and how to fix it · Last updated · By Ember, SniffPup
What does "Leaked Password Protection Disabled" mean?
Supabase Auth can reject passwords that have been leaked before. When the setting is on, it checks new passwords against the open-source HaveIBeenPwned Pwned Passwords API and refuses the ones attackers already know. The Security Advisor warning (it appears as auth_leaked_password_protection in advisor output) means that check is off.
The warning doesn't tell you whether anything has leaked from your project; it is about which passwords your forms accept. Supabase's docs say there are hundreds of millions of known leaked passwords, and attackers use these lists for automated sign-in attempts, which the docs call credential stuffing. Reusing a known leaked password increases the risk of account compromise.
It is an Auth setting, not a database lint, so you won't find it in the database lint list and no SQL clears it. You fix it in the dashboard or with the Management API.
How do I fix it?
On the Pro plan and above
Open your project, go to Authentication → Sign In / Providers → Email, turn on the option to prevent the use of leaked passwords, and save. While you are there, set the minimum password length and required characters too.
Prefer the API? The Management API's auth config endpoint (PATCH /v1/projects/{ref}/config/auth) has a password_hibp_enabled field. Every request needs an access token in the Authorization header, such as a personal access token you generate in your Supabase account. Keep it out of chats, screenshots and client code, and send:
curl -s -X PATCH "https://api.supabase.com/v1/projects/$PROJECT_REF/config/auth" \
-H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "password_hibp_enabled": true, "password_min_length": 8 }'On the Free plan
Supabase lists leaked password protection as available on the Pro Plan and above, so the switch won't turn on and the warning stays. You can still make passwords harder to guess in the same Email settings:
- Set the minimum password length to 8 or more. Supabase says anything less than 8 characters is not recommended.
- Require digits, lowercase and uppercase letters, and symbols. Supabase calls this the strongest option.
- Offer multi-factor authentication and encourage password managers, as Supabase's docs suggest.
Show a clear error in your sign-up form
When Supabase Auth rejects a password, supabase-js returns an AuthWeakPasswordError with the code weak_password and a reasons list (length, characters or pwned):
import { isAuthWeakPasswordError } from "@supabase/supabase-js";
const { error } = await supabase.auth.signUp({ email, password });
if (isAuthWeakPasswordError(error)) {
if (error.reasons.includes("pwned")) {
showError("This password has appeared in a data breach. Please choose a different one.");
} else {
showError("Please choose a longer password with more kinds of characters.");
}
}Existing users are not locked out. Supabase's docs say they can still sign in with a current password that falls short of the new rules, and signInWithPassword returns a WeakPasswordError explaining why, so you can prompt them to change it.
Using Lovable, Bolt or Cursor? Paste this into the chat:
Supabase Security Advisor reports Leaked Password Protection Disabled. I will turn on leaked password protection in Authentication > Sign In / Providers > Email myself. Update my sign-up and change-password screens: when supabase-js returns AuthWeakPasswordError (code weak_password), show "This password has appeared in a data breach" if reasons includes "pwned", and a length/characters message otherwise. Keep the Management API access token out of client code. Show me the changes before you apply them.
How do I check the fix worked?
Rerun the Security Advisor; the warning should be gone. Then try to sign up a test account with a password that meets your length and character rules but is in breach lists. Password123! is one: the HaveIBeenPwned range API listed it 295,527 times when we checked. With protection on, sign-up should be rejected with weak_password; check that reasons includes pwned and that your form shows your message. A rejection for length or characters alone does not prove leaked password protection is working.
What should I do?
1. Open the Email provider settings
In the Supabase dashboard, go to Authentication, then Sign In / Providers, then Email. This is where Supabase's password security docs link for password strength and leaked password protection.
2. Turn on leaked password protection (Pro plan and above)
Switch on the option to prevent the use of leaked passwords and save. On the Free plan this option is not available, so go to the next step.
3. Set a minimum length and required characters
Supabase says anything less than 8 characters is not recommended, and recommends the strongest required-characters option: digits, lowercase and uppercase letters, and symbols.
4. Handle the weak password error in your app
Catch AuthWeakPasswordError (code weak_password) on sign-up and password change, and show a clear message when reasons includes pwned.
5. Run the Security Advisor again
Open Advisors, then Security Advisor, and rerun it. The warning should be gone once leaked password protection is on.
Can SniffPup check this?
The free outside scan can't: it is passive and read-only, looks at what your published site gives any visitor, and Auth settings aren't visible from there. If you connect your Supabase project read-only, the Supabase project check (free with a SniffPup account) flags leaked password protection being off when it can read your Auth settings. What the outside scan does see, like a leaked service_role key in your JavaScript, is covered in Supabase security audit.
Next: Supabase security audit, Disable sign-ups for a private app, rls_disabled_in_public, and function_search_path_mutable.
FAQ
What does "Leaked Password Protection Disabled" mean?
Supabase's Security Advisor is telling you that Supabase Auth is not checking new passwords against known leaked passwords. With leaked password protection on, Supabase Auth uses the HaveIBeenPwned Pwned Passwords API to reject passwords that have been leaked and are known to attackers. It is an Auth setting, not a table or policy, so no SQL fixes it.
Does this warning mean my users' passwords leaked?
Not by itself. The warning doesn't tell you whether anything has leaked from your project. It means leaked password protection is off, so passwords in public breach lists may still be accepted if they meet your other password rules. Attackers use lists of leaked passwords for automated sign-in attempts, which Supabase's docs call credential stuffing.
Is leaked password protection free?
Supabase's password security docs say leaked password protection is available on the Pro Plan and above. On the Free plan you can still set a minimum password length and required characters, which Supabase also recommends.
What happens to existing users when I turn it on?
Supabase's docs say existing users can still sign in with their current password even if it doesn't meet the stronger rules. If it falls short, signInWithPassword returns a WeakPasswordError explaining why. New sign-ups and password changes must meet the new rules.
How do I show a helpful error in my sign-up form?
When Supabase Auth rejects a password, supabase-js returns an AuthWeakPasswordError with the code weak_password and a reasons list that can include length, characters or pwned. Check isAuthWeakPasswordError(error), and when reasons includes pwned, tell the user the password has appeared in a data breach and to choose a different one.
Can a SniffPup scan find this?
Not the free outside scan. It is passive and read-only on a live URL you own or are authorized to test, and Auth settings are not visible from the outside. If you connect your Supabase project read-only, SniffPup's Supabase project check (free with a SniffPup account) flags leaked password protection being off when it can read your Auth settings.
Sources: Supabase: Password security (leaked password protection, HaveIBeenPwned, Pro Plan and above, minimum length and required characters, existing users and WeakPasswordError), Supabase: Advisors (where Security Advisor runs), Supabase: Auth error codes (weak_password), supabase-js: AuthWeakPasswordError (reasons length, characters, pwned), Supabase Management API: update auth config (password_hibp_enabled) and HaveIBeenPwned: Pwned Passwords, checked November 14, 2026.