# CVE-2025-65431: django-allauth β€” Fixed in 65.13.0 🐍 🐍 PyPI Not in CISA KEV MEDIUM severity # CVE-2025-65431 β€” django-allauth MEDIUM [Fix: pennersr/django-allauth@8feef46](https://github.com/pennersr/django-allauth/commit/8feef46e0e07b25fc5594c8f268afa247ebc3412) CVE-2025-65431 is a medium-severity (CVSS 5.4) Improper Authentication vulnerability in django-allauth. A fix is available for django-allauth β€” see the affected versions and patch details below. django-allauth's Okta and NetIQ implementations used a mutable identifier for authorization decisions Also known as[GHSA-8m3c-c723-h4p4](/vulnerability/GHSA-8m3c-c723-h4p4)PYSEC-2025-111 Published Dec 15, 2025 Updated Oct 28, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 3, 2026 Β· OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-65431. ## EPSS Exploitation Probability [via FIRST.org β†—](https://www.first.org/epss/) 0.2%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs6th percentile β€” riskier than 6% of all scored CVEsHighest risk 0.00%0.22%0.44%0.66%0.0%0.2%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 1 pkg affected 🐍`django-allauth` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages β€” download data is not available via public APIs for these ecosystems. ## Description An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred\_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 🐍PyPI `django-allauth` all versions 65.13.0`pip install --upgrade 'django-allauth==65.13.0'` ## Affected Products 1 product Β· 1 configurations Application `allauth`allauth < 65.13.0 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-allauth, including transitive dependencies β€” a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update django-allauth to 65.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range β€” O3 confirms CVE-2025-65431 is resolved across your whole dependency graph. 3. ### Workarounds Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used. ## Frequently Asked Questions An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred\_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead. O3 Security Β· Impact-Aware SCA ### Is CVE-2025-65431 in your dependencies? Find it across PyPI, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)