Is CVE-2025-65430 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-65430 being exploited in the wild.

How severe is CVE-2025-65430?

Medium severity, with a CVSS score of 5.4, published 15 December 2025.

Which products and versions are affected?

django-allauth (PyPI) < 65.13.0, ECOSYSTEM:introduced=0,fixed=65.13.0.

Is there a fix for CVE-2025-65430?

Yes. django-allauth (PyPI): upgrade to 65.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-65430 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-65430?

Check whether you run Allauth or django-allauth (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-65430: django-allauth insufficient session expiration for inactive users

Q: Is there a fix for CVE-2025-65430?

Yes. django-allauth (PyPI): upgrade to 65.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2025-65430 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2025-65430?

Check whether you run Allauth or django-allauth (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-65430 · Severity: medium · CVSS 5.4 · Published 2025-12-15

django-allauth is a popular authentication and registration package for the Django web framework. A security issue was identified where the software failed to revoke access for users who were marked as inactive. This means that if an administrator disables a user's account, any existing login tokens held by that user would remain valid, potentially allowing unauthorized access to the system until those tokens naturally expire.

Technologies: django-allauth (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2025-65430 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-65430 being exploited in the wild.
How severe is CVE-2025-65430?: Medium severity, with a CVSS score of 5.4, published 15 December 2025.
Which products and versions are affected?: django-allauth (PyPI) < 65.13.0, ECOSYSTEM:introduced=0,fixed=65.13.0.
Is there a fix for CVE-2025-65430?: Yes. django-allauth (PyPI): upgrade to 65.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-65430 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-65430?: Check whether you run Allauth or django-allauth (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

django-allauth (PyPI): upgrade to 65.13.0 or later
```
pip install "django-allauth>=65.13.0"
```

Technical details

A vulnerability classified as Insufficient Session Expiration (CWE-613) exists in django-allauth's Identity Provider (IdP) implementation. The root cause is a missing check for the 'is_active' status of a user during token validation in the OIDC/OAuth2 request validator. An attacker with a previously issued, valid access or refresh token can continue to authenticate and access protected resources even after their account has been disabled by an administrator. The issue is resolved in version 65.13.0 by adding explicit checks for 'user.is_active' in the 'validate_bearer_token' and 'validate_refresh_token' methods.

Affected products

pennersr django-allauth < 65.13.0

Identifiers

CVE-2025-65430
GHSA-qhmc-3mvr-f2j4
PYSEC-2025-110

Timeline

2025-10-31: patched: Version 65.13.0 released
2025-12-15: disclosed: CVE-2025-65430 published
2025-12-15: advisory: GitHub Advisory GHSA-qhmc-3mvr-f2j4 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.