Persistent IdP access via missing user-status checks
Published Dec 15, 2025 · Updated Dec 15, 2025
Insufficient session expiration in django-allauth before 65.13.0 allows remote authenticated users to retain IdP token access. The OIDC request validator accepts access and refresh tokens without checking whether the associated Django user remains active. Exploitation requires a token issued while the account was active; that token continues to authorize protected resources and token refresh after deactivation.
Summary
What happened
Insufficient session expiration in django-allauth before 65.13.0 allows remote authenticated users to retain IdP token access. The OIDC request validator accepts access and refresh tokens without checking whether the associated Django user remains active. Exploitation requires a token issued while the account was active; that token continues to authorize protected resources and token refresh after deactivation.
The record
- CVE
- CVE-2025-65430
- Published
- Dec 15, 2025
- Updated
- Dec 15, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 15, 2025CVE publishedPublication date reported by the CVE source.
- Dec 15, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo