CVE-2025-65430: Django allauth Django-allauth Does Not Reject Access Vulnerability

MODERATE
Advisory Identifier: GHSA-qhmc-3mvr-f2j4
Share
CVSS 5.4
CWE-613
Published
Advisory Summary

CVE-2025-65430 is a MODERATE (CVSS 5.4) django-allauth does not reject access vulnerability (CWE-613: Insufficient Session Expiration) affecting Django allauth libraries in the PyPI ecosystem. The issue involves django-allauth does not reject access tokens for inactive users. Remediation is available by upgrading affected packages to version 65.13.0.

CVE-2025-65430 at a Glance

CVE Identifier CVE-2025-65430
GHSA Identifier GHSA-qhmc-3mvr-f2j4
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product Django allauth
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2025-65430

To remediate this vulnerability, upgrade all affected Django allauth dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

django-allauth fixed: 65.13.0 
pip install django-allauth>=65.13.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show django-allauth

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2025-65430, inspect your installed packages using pip:

pip show django-allauth

Analyze the terminal output to locate any version of Django allauth in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 65.13.0), your application is affected.

Note: The pip show django-allauth command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In Django allauth, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2025-65430 Affected Django allauth Versions

1 component(s)
Fixed Versions:
65.13.0
Product / Package Ecosystem Affected Versions Fixed Version
django-allauth
pypi/django-allauth
PyPI
< 65.13.0
65.13.0

References

NVD — CVE-2025-65430 NVD
https://nvd.nist.gov/vuln/detail/CVE-2025-65430
Security Fix Commit FIX COMMIT
https://github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0
Security Fix Commit FIX COMMIT
https://github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d
allauth.org/news/2025/10/django... WEB
https://allauth.org/news/2025/10/django-allauth-65.13.0-released
codeberg.org/allauth/django-alla... PACKAGE
https://codeberg.org/allauth/django-allauth
Django allauth Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml

Frequently Asked Questions

What is CVE-2025-65430?
CVE-2025-65430 is a security vulnerability in Django allauth involving django-allauth does not reject access tokens for inactive users under CWE-613: Insufficient Session Expiration.
Which Django allauth versions are affected?
Affected versions include releases prior to 65.13.0 across affected packages: django-allauth.
What version fixes CVE-2025-65430?
Upgrading to 65.13.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is django-allauth affected?
Yes, django-allauth is affected in releases prior to 65.13.0. Upgrade your dependency to 65.13.0 or later.
What is the CVSS score of CVE-2025-65430?
CVE-2025-65430 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2025-65430?
CVE-2025-65430 is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check PyPI dependencies for CVE-2025-65430?
Run the dependency tree command: 'pip show django-allauth'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qhmc-3mvr-f2j4",
  "modified" : "2026-06-05T14:34:45Z",
  "published" : "2025-12-15T15:30:31Z",
  "aliases" : [ "CVE-2025-65430" ],
  "summary" : "django-allauth does not reject access tokens for inactive users",
  "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "django-allauth"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "65.13.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-65430"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pennersr/django-allauth/commit/39f4a4ce9c891795b00914ca5ec32de72d5369c0"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pennersr/django-allauth/commit/c54edf947c5a1c8c4ff3cddb75c86000ecb2507d"
  }, {
    "type" : "WEB",
    "url" : "https://allauth.org/news/2025/10/django-allauth-65.13.0-released"
  }, {
    "type" : "PACKAGE",
    "url" : "https://codeberg.org/allauth/django-allauth"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/django-allauth/PYSEC-2025-110.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-613" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-16T19:33:33Z",
    "nvd_published_at" : "2025-12-15T14:15:57Z"
  }
}