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.
CVE-2026-97764
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(low)
- EG Risk
- 21(Track)EG Risk 21/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 25, 2026
Last Modified
September 25, 2026
References (5)
- cve@mitrehttps://codeberg.org/allauth/django-allauth/commit/4379e7931fe7572aacc4f3b4b5f2298d5f3ecc96
- cve@mitrehttps://codeberg.org/allauth/django-allauth/commit/4e252aa2be7cef5d72d78049d6fb07cb27a89c83
- cve@mitrehttps://codeberg.org/allauth/django-allauth/commit/ae472772c8f93bcb972205c9d7159051cf6f413a
- cve@mitrehttps://docs.allauth.org/en/latest/release-notes/recent.html
- cve@mitrehttps://pypi.org/project/django-allauth/
Vendor Advisories for CVE-2026-97764(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-25 05:26 UTCEG score recompute
- 2026-09-25 04:32 UTCEG score recompute
- 2026-09-25 04:32 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-97764?
When was CVE-2026-97764 disclosed?
What is the CVSS score of CVE-2026-97764?
How do I remediate CVE-2026-97764?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-97764
Is Your Infrastructure Affected by CVE-2026-97764?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.