← Back
CVE-2026-27982
Open Redirect in django-allauth (CVE-2026-27982)
Summary
vulnerability in django-allauth (CVE-2026-27982). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `65.14.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-27982** has been found in django-allauth.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade django-allauth to **65.14.1** or later.
If unsure, ask your IT team or search "django-allauth CVE-2026-27982" on the vendor's site.
CVE-2026-27982 (django-allauth) — CWE-601 /
Attack vector: remote (network-reachable) / unauthenticated
Patched: `65.14.1` — 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
**A vulnerability** (CWE-601) exists in django-allauth.
📍 Affected scope
django-allauth — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **65.14.1**.
🛡️ 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.14.1ステージング環境で 65.14.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.14.1"}]}]
pip
django-allauth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"65.14.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-27982
- advisory https://allauth.org/news/2026/02/django-allauth-65.14.1-released/
- advisory https://jvn.jp/en/jp/JVN23669411/
- advisory https://github.com/advisories/GHSA-2jpr-83rg-v67j
- package https://github.com/pennersr/django-allauth
- web https://allauth.org/news/2026/02/django-allauth-65.14.1-released
- web https://jvn.jp/en/jp/JVN23669411
- web https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2026-56.yaml