CVE-2025-65430: django-allauth does not reject access tokens for inactive users
Medium CVSS 5.4
- OSV id
- GHSA-qhmc-3mvr-f2j4
- Also known as
- CVE-2025-65430, PYSEC-2025-110
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| django-allauth PyPI |
< 65.13.0 | 65.13.0 |
Versions we track that it affects: django-allauth 0.63.3
How to fix it
Upgrade django-allauth to 65.13.0 or later.
# in requirements.txt: change the line to django-allauth==65.13.0
pip install -r requirements.txt
- If it is an indirect dependency, upgrade the package that depends on it, or add a minimum version constraint for it (e.g. in constraints.txt, or as a dependency in pyproject.toml).
- Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.
Not sure whether your project uses an affected version? Check your lockfile below for free.
Details
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.
References
- GHSA-qhmc-3mvr-f2j4 on OSV.dev
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-65430
- Web: 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
- Package: https://codeberg.org/allauth/django-allauth
- Web: https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.