CVE-2025-65430 django-allauth does not reject access tokens for inactive users
Attackers can retain access using previously issued tokens even after an account is deactivated, bypassing intended authentication controls.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-65430?
CVE-2025-65430 is a medium-severity authentication bypass vulnerability in n/a, published on 15 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-613
Which versions are affected by CVE-2025-65430?
3 open source packages ship an affected version, including django-allauth. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
django-allauth PyPI | All versions | 65.13.0 |
django-allauth PyPI | All versions | 65.13.0 |
django-allauth PyPI | All versions | 65.13.0 |
Products include Allauth Allauth.
How do I fix CVE-2025-65430?
Upgrade django-allauth to 65.13.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-65430 being exploited?
There is no known exploitation of CVE-2025-65430 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as DEBIAN-CVE-2025-65430, GHSA-qhmc-3mvr-f2j4, PYSEC-2025-110, UBUNTU-CVE-2025-65430.