CVE-2026-97764
Received Received - Intake

Authentication Bypass via Diacritic Handling in django-allauth

Vulnerability report for CVE-2026-97764, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-25

Last updated on: 2026-09-25

Assigner: MITRE

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-25
Last Modified
2026-09-25
Generated
2026-09-25
AI Q&A
2026-09-25
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
django-allauth django-allauth to 65.19.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-180 The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

django-allauth before version 65.19.4 has a flaw in its authentication system where failed login attempts are not properly limited. This happens because usernames or emails with diacritics (like accents) can bypass rate limits by creating multiple keys for a single account. For example, 'admin' and 'Γ‘dmin' might be treated as different accounts during login attempts.

Detection Guidance

To detect this vulnerability, check if you are using django-allauth versions up to 65.19.4. Inspect authentication logs for multiple failed login attempts from the same account using variations with diacritics (e.g., 'admin' vs 'Γ‘dmin'). Ensure your AUTHENTICATION_BACKENDS does not include Django’s ModelBackend if using username authentication.

Impact Analysis

Attackers could exploit this to repeatedly attempt logging into your account without triggering rate limits. This increases the risk of brute-force attacks, potentially allowing unauthorized access if weak passwords are used. Systems relying on django-allauth for authentication may face higher security risks.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by weakening authentication security. Bypassing rate limits may allow unauthorized access attempts to go undetected, increasing the risk of data breaches or unauthorized data access. GDPR requires strong security measures to protect personal data, while HIPAA mandates strict access controls for protected health information. The vulnerability undermines these requirements by enabling attackers to circumvent login attempt limits.

Mitigation Strategies

Upgrade django-allauth to version 65.19.4 or later. If using username authentication, remove Django’s ModelBackend from AUTHENTICATION_BACKENDS. Review authentication logs for suspicious activity and enforce stricter rate limits on login attempts.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-97764. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart