← Back
CVE-2025-65431
Authentication Bypass in django-allauth (CVE-2025-65431)
Summary
authentication bypass in django-allauth (CVE-2025-65431). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `65.13.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-65431** has been found in django-allauth.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade django-allauth to **65.13.0** or later.
If unsure, ask your IT team or search "django-allauth CVE-2025-65431" on the vendor's site.
CVE-2025-65431 (django-allauth) — CWE-287 /
Attack vector: remote (network-reachable) / no user interaction
Patched: `65.13.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**authentication bypass** (CWE-287) exists in django-allauth.
📍 Affected scope
django-allauth — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **65.13.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'django-allauth' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'django-allauth' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `django-allauth` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade django-allauth to 65.13.0ステージング環境で 65.13.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
django-allauth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"65.13.0"}]}]
pip
django-allauth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"65.13.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-65431
- advisory https://allauth.org/news/2025/10/django-allauth-65.13.0-released/
- advisory https://github.com/advisories/GHSA-8m3c-c723-h4p4
- package https://codeberg.org/allauth/django-allauth
- web https://github.com/pennersr/django-allauth/commit/8feef46e0e07b25fc5594c8f268afa247ebc3412
- web https://allauth.org/news/2025/10/django-allauth-65.13.0-released
- web https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-111.yaml