cve.bz

CVE-2025-65430 allauth allauth: Insufficient Session Expiration

5.4 mediumEPSS 0.2%Fix available

Medium (5.4) in allauth allauth. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in django-allauth 65.13.0.

On this page
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

CVSS 3.1

5.4 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-12-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-613 Insufficient Session Expiration deprecated by MITRE see CWE-1463, CWE-1464
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-65430 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-65430?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-65430?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-65430 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
allauth:allauthbefore 65.13.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qhmc-3mvr-f2j4PyPIdjango-allauth<65.13.065.13.0
PYSEC-2025-110PyPIdjango-allauth<65.13.065.13.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13django-allauthno fix listedDEBIAN-CVE-2025-65430
Debian14django-allauth65.15.0-1DEBIAN-CVE-2025-65430
Ubuntu18.04:LTS, 20.04:LTS, 22.04:LTS and 4 moredjango-allauthno fix listedUBUNTU-CVE-2025-65430
openSUSETumbleweedpython-django-allauth65.16.1-2.1openSUSE-SU-2026:10680-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

References

Check your stackJSON