CVE-2026-97764 PUBLISHED

django-allauth before 65.19.4 does not have the expected limits on failed login attempts because, in some common configurations, an attacker can leverage the handling of diacritics (e.g., accents) for a higher effective limit.

1. Any of the following settings is enabled in Django configuration.

65.4 and later: ACCOUNT_LOGIN_METHODS = {"username", "email"} ACCOUNT_LOGIN_METHODS = {"username"}

65.3 and earlier: ACCOUNT_AUTHENTICATION_METHOD = "username_email" ACCOUNT_AUTHENTICATION_METHOD = "username"

1. The username column in the database uses a collation such as utf8mb4_general_ci or utf8mb4_unicode_ci.

The vulnerability is NOT exposed if any of the following settings is enabled.

65.4 and later: ACCOUNT_LOGIN_METHODS = {"email"}

65.3 and earlier: ACCOUNT_AUTHENTICATION_METHOD = "email"

Upgrade django-allauth to version 65.19.4 (latest).

• https://docs.allauth.org/en/latest/release-notes/recent.html
• https://pypi.org/project/django-allauth/
• https://codeberg.org/allauth/django-allauth/commit/4379e7931fe7572aacc4f3b4b5f2298d5f3ecc96
• https://codeberg.org/allauth/django-allauth/commit/4e252aa2be7cef5d72d78049d6fb07cb27a89c83
• https://codeberg.org/allauth/django-allauth/commit/ae472772c8f93bcb972205c9d7159051cf6f413a

• CWE-180 Incorrect Behavior Order: Validate Before Canonicalize CWE