Is django-allauth 65.14 vulnerable?
PyPI · 4 releases from 65.14.0 to 65.14.3 · latest django-allauth is 65.22.1 · checked 18 Nov 2026
No known advisories in the last release
django-allauth 65.14.3, the last 65.14 release, has no known advisories. 1 advisory affects earlier 65.14.x releases, so update to 65.14.3.
pip install 'django-allauth>=65.14.3'Is your project on an affected django-allauth?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 65.14.x, affecting earlier releases
django-allauth has an open redirect vulnerability
- Affected
- <65.14.1
- Fixed in
- 65.14.1
Every django-allauth 65.14.x release
Affected: 65.14.0. 65.14.1 and later are not affected. Latest django-allauth: 65.22.1.
| Version | Known advisories |
|---|---|
| django-allauth 65.14.3 | None |
| django-allauth 65.14.2 | None |
| django-allauth 65.14.1 | None |
| django-allauth 65.14.0 | CVE-2026-27982 |
Which of your client projects are still on django-allauth 65.14?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact django-allauth version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other django-allauth versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.