Description
An issue was discovered in allauth-django before 65.13.0. IdP: marking a user as is_active=False after having handed tokens for that user while the account was still active had no effect. Fixed the access/refresh tokens are now rejected.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Debian
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian 14 | django-allauth | 65.15.0-1 | — |
| Debian 13 | django-allauth | No fix yet | — |
| Debian 12 | django-allauth | No fix yet | — |
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 26.10 | django-allauth | No fix yet | — |
| Ubuntu 26.04 LTS | django-allauth | No fix yet | — |
| Ubuntu 25.10 | django-allauth | No fix yet | — |
| Ubuntu 24.04 LTS | django-allauth | No fix yet | — |
| Ubuntu 22.04 LTS | django-allauth | No fix yet | — |
Show 2 more (older releases, extended support, other products)Fewer releases
| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 20.04 LTS | django-allauth | No fix yet | — |
| Ubuntu 18.04 LTS | django-allauth | No fix yet | — |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | python-django-allauth | 65.16.1-2.1 | openSUSE-SU-2026:10680-1 |
Affected packages
| Ecosystem | Package | Affected | Fixed | Record |
|---|---|---|---|---|
| PyPI | django-allauth | < 65.13.0 | 65.13.0 | GHSA-qhmc-3mvr-f2j4 |
Advisories 1
- openSUSE-SU-2026:10680-1 python311-django-allauth-65.16.1-2.1 on GA media SUSE / openSUSE Security Updates · May 5, 2026