An issue exists where the registration process and the email uniqueness constraint treat email addresses as case-sensitive, whereas the login lookup is case-insensitive. An unauthenticated attacker can register a variant of a victim's email address with different casing via the 'POST /api/v1/users/register' endpoint. This creates duplicate entries for the `email` variable, which results in a 401 error for both accounts during login, effectively denying the victim access and bypassing the policy that restricts users to one account per email.