CVE-2025-65430
2 advisories.
PyPI/django-allauth CVE-2025-65430: medium 5.4, EPSS 0.17%
django-allauth does not reject access tokens for inactive users
Action: Upgrade django-allauth to 65.13.0 or later.
pip install django-allauth==65.13.0Affected
| introduced | fixed | last affected |
|---|---|---|
| 0 | 65.13.0 | - |
Fixed versions
| 65.13.0 |
Sources
- osv: GHSA-qhmc-3mvr-f2j4
- https://nvd.nist.gov/vuln/detail/CVE-2025-65430
- https://github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0
- https://github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d
- https://allauth.org/news/2025/10/django-allauth-65.13.0-released
- https://codeberg.org/allauth/django-allauth
- https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml
CVE-2025-65430 · published · modified · JSON
PyPI/django-allauth CVE-2025-65430: medium 5.4, EPSS 0.17%
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 ac
Action: Upgrade django-allauth to 65.13.0 or later.
pip install django-allauth==65.13.0Affected
| introduced | fixed | last affected |
|---|---|---|
| 0 | 65.13.0 | - |
Fixed versions
| 65.13.0 |
Sources
- osv: PYSEC-2025-110
- https://allauth.org/news/2025/10/django-allauth-65.13.0-released/
- https://github.com/advisories/GHSA-qhmc-3mvr-f2j4
CVE-2025-65430 · published · modified · JSON