CVE-2025-65430
django-allauth does not reject access tokens for inactive users
Reported by mitre · Published December 15, 2025
django-allauth is fixed in 65.13.0 (PyPI)
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| django-allauth | PyPI | 65.13.0 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| PyPI | django-allauth | 0 |
| n/a | n/a | * |
Timeline
- Dec 15, 2025 CVE Published
- Dec 16, 2025 EPSS Score (30 in total, the first dated here)
- Mar 9, 2026 Security Advisory
- Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
- Jun 17, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-65430
vulnetix vdb fixes CVE-2025-65430
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-65430/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- https://nvd.nist.gov/vuln/detail/CVE-2025-65430 advisory
- https://github.com/advisories/GHSA-qhmc-3mvr-f2j4 advisory
- https://allauth.org/news/2025/10/django-allauth-65.13.0-released url
- https://github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0 patch
- https://github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d patch
- https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml advisory