Advisory Database
  • Advisories
  • Dependency Scanning
  1. pypi
  2. ›
  3. django-allauth
  4. ›
  5. CVE-2025-65430

CVE-2025-65430: django-allauth does not reject access tokens for inactive users

December 15, 2025 (updated December 16, 2025)

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

  • allauth.org/news/2025/10/django-allauth-65.13.0-released
  • codeberg.org/allauth/django-allauth
  • github.com/advisories/GHSA-qhmc-3mvr-f2j4
  • github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0
  • github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d
  • nvd.nist.gov/vuln/detail/CVE-2025-65430

Code Behaviors & Features

Detect and mitigate CVE-2025-65430 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions before 65.13.0

Fixed versions

  • 65.13.0

Solution

Upgrade to version 65.13.0 or above.

Impact 5.4 MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Learn more about CVSS

Weakness

  • CWE-613: Insufficient Session Expiration

Source file

pypi/django-allauth/CVE-2025-65430.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 04 Feb 2026 00:35:55 +0000.