CVE-2025-65430
Allauth vulnerability
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.
Affected products
Allauth. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Allauth runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- allauth.org/news/2025/10/django-allauth-65.13.0-released/
- nvd.nist.gov/vuln/detail/CVE-2025-65430
- allauth.org/news/2025/10/django-allauth-65.13.0-released
- github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0
- github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d
- github.com/advisories/GHSA-qhmc-3mvr-f2j4
- github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml
- nvd.nist.gov/vuln/detail/CVE-2025-65430
- cve.org/CVERecord?id=CVE-2025-65430
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.