GitHub Advisoryadvisory · PyPI
GHSA-qhmc-3mvr-f2j4 django-allauth does not reject access tokens for inactive users
MEDIUM
Official page ↗
- Aliases
- CVE-2025-65430
- Ecosystem
- PyPI
- Packages
- django-allauth
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
- Weaknesses
- CWE-613
- Reviewed
- 2025-12-16
Affected packages
• PyPI django-allauth: < 65.13.0 → fixed in 65.13.0
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.
Related
Weakness · not in database (1)
Alias · CVE (1)
- CVE-2025-65430 An issue was discovered in allauth-django before 65.13.0. vulnerability
References
- https://nvd.nist.gov/vuln/detail/CVE-2025-65430 advisory
- https://github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0 web
- https://github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d web
- https://allauth.org/news/2025/10/django-allauth-65.13.0-released web
- https://codeberg.org/allauth/django-allauth package
- https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml web