Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of django-allauth before 65.13.0 are affected. When the identity provider (IdP) functionality is used, setting a user's is_active flag to False after tokens were already issued for that user while the account was active had no effect, so the tokens kept working. The source gives few details on the exact conditions or who could exploit this. Upgrade to django-allauth 65.13.0 or later, where access and refresh tokens are rejected once the user is deactivated.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.4 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N | OSV |
- CISA KEV Not listed.
- EPSS 0.0018, the 7th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.