CVE-2025-65430: django-allauth does not reject access tokens for inactive users
An issue was discovered in allauth-django before 65.13.0. IdP: marking a user as isactive=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.
Published Dec 15, 2025 · Updated Jun 5, 2026
Affected packages
django-allauth
- Ecosystem
- PyPI
- Affected
- < 65.13.0
- Fixed in
- 65.13.0
- Check
pip show django-allauth
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2025-65430
- https://allauth.org/news/2025/10/django-allauth-65.13.0-released
- https://github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0
- https://github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d
- https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml
- https://github.com/advisories/GHSA-qhmc-3mvr-f2j4
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
