VDB

CVE-2025-65430

CVE-2025-65430 PUBLISHED CVSS 5.400000095367432 MEDIUM

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.

PackageEcosystemFixed in
django-allauthPyPI65.13.0

Risk scores

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

Affected products

VendorProductVersions
n/an/an/a
PyPIdjango-allauth0
n/an/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

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›