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

PackageAffected versionsFixed 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

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.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

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.