Guide
weak_password
How this guide was made: Written with AI assistance and checked against the sources linked on this page.
Updated
Short answer: Supabase returns the error code weak_password when a sign-up or password change uses a password that fails the project's password rules. The rules can check length, required character sets and a list of leaked passwords. The error lists the reasons, so read them, then choose a password that passes every rule.
What does weak_password mean?
weak_password means the password did not meet the strength criteria the project sets. Supabase's error page describes it as "User is signing up or changing their password without meeting the password strength criteria" (Supabase: Auth error codes).
The Auth server returns it with HTTP 422 and puts the list of reasons under a weak_password key (supabase/auth: errors.go). The reason codes are length, characters and pwned (supabase/auth: password.go).
The message text comes from the same checks: "Password should be at least %d characters." for length, "Password should contain at least one character of each: %s." for a missing character set, and "Password is known to be weak and easy to guess, please choose a different one." for a leaked password (supabase/auth: password.go).
Which cause is it?
| What you see | Cause | Fix |
|---|---|---|
Reason length, or "Password should be at least N characters." | The password is shorter than the minimum | Cause 1 |
Reason characters, or "Password should contain at least one character of each" | The password is missing a required character set | Cause 2 |
Reason pwned, or "Password is known to be weak and easy to guess" | The password appears in a leaked password list | Cause 3 |
| The error comes at sign-in for an existing user | The account's old password does not meet the new rules | Cause 4 |
1. The password is shorter than the minimum length
The Supabase password security page says: "Set a large minimum password length. Anything less than 8 characters is not recommended." (Supabase: Password security). The Auth server compares the password's character count with the project's minimum length and adds the reason length when it is too short (supabase/auth: password.go).
How to fix it
- Check the minimum length the project requires. The Auth source reads it as config.Password.MinLength.
- Enter a password with at least that many characters. The check counts characters, not bytes.
- If you set the minimum yourself, keep it at 8 or more. The docs say anything under 8 is not recommended.
Source: Supabase: Password security, supabase/auth: password.go
2. The password is missing a required character set
The Supabase password security page says to "Set the required characters that must appear at least once in a user's password," and to "Use the strongest option of requiring digits, lowercase and uppercase letters, and symbols" (Supabase: Password security). The Auth server adds the reason characters for the first set the password lacks, and then stops checking the remaining sets (supabase/auth: password.go).
How to fix it
- Read which character sets your project requires.
- Add at least one character from each set, such as a digit, an uppercase letter and a symbol.
- Our suggestion: try again. Because the check stops at the first missing set, a second missing set can show up after the first is fixed.
Source: Supabase: Password security, supabase/auth: password.go
3. The password appears in a leaked password list
The Auth server checks the password against HaveIBeenPwned.org when that check is turned on. A match adds the reason pwned (supabase/auth: password.go). Supabase says leaked password protection "will reject passwords that have been leaked and are known by malicious actors," and that it "is available on the Pro Plan and above" (Supabase: Password security).
How to fix it
- Choose a password that is not from a known leak.
- If you are the project owner, check whether the leaked password setting is on. The docs say it is available on the Pro Plan and above, so this reason does not apply on plans without it.
- If the check cannot reach HaveIBeenPwned.org, the result depends on the FailClosed setting in the Auth source. With it on, the sign-up returns "Unable to perform password strength check with HaveIBeenPwned.org." With it off, the password is allowed and a warning is logged (supabase/auth: password.go).
Source: Supabase: Password security, supabase/auth: password.go
4. An existing user signs in with an old password
The Supabase password security page says that existing users "can still sign in with their current password even if it doesn't meet the new, strengthened password requirements," and that users whose password "falls short of these updated standards" "will encounter a WeakPasswordError during the signInWithPassword process, explaining why it's considered weak" (Supabase: Password security).
How to fix it
- Show the person the reasons from the error, so they know which rule the old password fails.
- Send a password reset. The Supabase passwords page describes
resetPasswordForEmail(), which does not reveal whether an account exists (Supabase: Passwords). - Have the person set a new password that passes all the rules, then sign in with it.
Source: Supabase: Password security, Supabase: Passwords
How do I check it's fixed?
- Our suggestion: in a private window on your live app, sign up with a password that is too short. Expect weak_password with the reason
length. This shows the check runs. - Our suggestion: sign up with a password that passes every rule. Expect the sign-up to continue.
- Our suggestion: in the same window, change the password with one that fails one rule. Expect the error and its reason. Then change it with a password that passes, and expect the change to succeed.
FAQ
What HTTP status does weak_password use?
The Auth server returns HTTP 422 for it (supabase/auth: errors.go). The error class is AuthWeakPasswordError, which Supabase says gives more detail about the reasons (Supabase: Auth error codes).
Where do I read the reasons?
The reasons come back under the weak_password key of the error response (supabase/auth: errors.go).
Is there a maximum password length?
Yes. The Auth server sets the maximum at 72 characters for BCrypt. A longer password gets a separate bad request with the message "Password cannot be longer than %v characters", not the weak_password code (supabase/auth: password.go).
Can VibeFix fix it for me?
Yes, for apps built in Lovable or any app whose code is on GitHub. The free check confirms the problem on your live app first. If you want it fixed, our AI agent finds the cause, fixes it in your code for $79 and tests your live app again. See pricing.
Related guides
- Supabase invalid login credentials: the fix
- Supabase reset password email not sending
- Supabase signups not allowed for this instance
Sources (official documentation)
- Supabase: Auth error codes
- Supabase: Password security
- Supabase: Passwords
- supabase/auth: internal/api/password.go
- supabase/auth: internal/api/errors.go
- supabase/auth: internal/api/apierrors/errorcode.go
Last checked: 17 November 2026.
VibeFix is independent. Supabase is a trademark of its owner.
More guides · Shopify store accessibility · About · Your privacy choices