# CVE-2026-97764: Security feature bypass in django-allauth

> Attackers can bypass failed login attempt limits by leveraging diacritic handling in specific configurations, allowing for brute-force attacks.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** DEBIAN-CVE-2026-97764, GHSA-qwgm-hfpp-4pf6, UBUNTU-CVE-2026-97764, openSUSE-SU-2026:11903-1

## What is CVE-2026-97764?

CVE-2026-97764 is a low-severity vulnerability in django-allauth, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-97764?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `python-django-allauth` | openSUSE:Tumbleweed | All versions | 65.19.4-1.1 |

## How do I fix CVE-2026-97764?

Upgrade to a fixed version.

## Is CVE-2026-97764 being exploited?

There is no known exploitation of CVE-2026-97764 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97764 and fix it if it is affected.

What it is: CVE-2026-97764 is a low-severity vulnerability in django-allauth, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97764 in the wild and no public exploit code.

Affected product: django-allauth. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97764/ (Markdown: https://insights.sbomify.com/CVE-2026-97764/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97764
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97764
- OSV: https://osv.dev/vulnerability/CVE-2026-97764

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97764/
Summaries are generated and may contain mistakes; the official description above is the record.