VulnerabilityPublished 15 Dec 2025

CVE-2025-65430: allauth-django · Insufficient Session Expiration

Affects allauth-djangoSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 65.13.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

5.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 65.13.0

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 15 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade allauth-django to 65.13.0.

Affected software

Product	Affected	Fixed in
PyPIallauth-django`pkg:pypi/allauth-django`Other threats	Affected <65.13.0	Fixed in 65.13.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify if they are using allauth-django versions prior to 65.13.0 and plan an upgrade to the latest patched release. In environments where immediate patching is not feasible, temporary mitigations include implementing additional token revocation mechanisms at the application or API gateway level, such as maintaining a blacklist of tokens associated with deactivated users. Monitoring and alerting on unusual token usage patterns, especially from accounts recently marked inactive, can help detect exploitation attempts. Organizations should also review their user deactivation workflows to ensure tokens are invalidated promptly and consider shortening token lifetimes to reduce exposure windows. Integrating multi-factor authentication (MFA) can further reduce risk by adding an additional verification layer. Finally, conducting regular security audits and penetration tests focusing on authentication flows will help identify similar weaknesses.

Description

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.

Impact

For European organizations, this vulnerability poses a risk of unauthorized access persistence even after user accounts are disabled, potentially leading to data leakage or unauthorized actions under the guise of a deactivated user. This can undermine trust in identity management systems and complicate compliance with regulations such as GDPR, which require strict access controls and timely revocation of user privileges. The impact is particularly significant for organizations handling sensitive personal data or critical infrastructure where user deactivation is a common security control. Since the vulnerability affects token invalidation, attackers could exploit it to maintain access without needing to reauthenticate, increasing the risk of insider threats or compromised accounts being leveraged for lateral movement. Although no availability impact is noted, the confidentiality and integrity risks warrant prompt remediation. The medium severity rating suggests this is a moderate but actionable threat that should be prioritized alongside other security updates.

CWE-613Insufficient Session Expiration (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
Implementation
Set sessions/credentials expiration date.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.1 (opens in a new tab)
V2.8.6 (opens in a new tab)
V3.6.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

allauth.org/news/2025/10/django-allauth-65.13.0-released/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Dec 2025, 14:41 UTC

WeaknessesCWE-613

Technical details

References

Community reviews

Related threats