Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-65431: n/a

0
Medium
VulnerabilityCVE-2025-65431cvecve-2025-65431
Published: Mon Dec 15 2025 (12/15/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferred_username as the identifier for third-party provider accounts. That value may be mutable and should therefore be avoided for authorization decisions. The providers are now using sub instead.

AI-Powered Analysis

AILast updated: 12/15/2025, 14:31:41 UTC

Technical Analysis

CVE-2025-65431 is a security vulnerability discovered in the allauth-django authentication library prior to version 65.13.0. The issue arises because the third-party authentication providers Okta and NetIQ used the 'preferred_username' attribute as the primary identifier for user accounts during authorization decisions. The 'preferred_username' attribute is mutable, meaning it can be changed by the user or the identity provider, which undermines its reliability as a stable identifier. This mutability can be exploited by attackers to impersonate other users or escalate privileges by altering the username value, thereby bypassing authorization controls. The vulnerability affects all versions of allauth-django before 65.13.0 that integrate with these providers. The fix implemented involves switching the identifier from 'preferred_username' to the 'sub' claim, which is a unique, immutable identifier assigned by the identity provider and is not subject to change. This change ensures that authorization decisions rely on a stable and tamper-resistant attribute. No CVSS score has been assigned yet, and no known exploits have been reported in the wild. However, the vulnerability poses a significant risk to applications relying on allauth-django for authentication with Okta or NetIQ, especially in environments where authorization is tightly coupled with user identity attributes. The issue highlights the importance of using immutable identifiers in authentication and authorization workflows to prevent identity spoofing and unauthorized access.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized access to sensitive systems and data if attackers manipulate the mutable 'preferred_username' attribute to impersonate other users or escalate privileges. This is particularly critical for enterprises using allauth-django integrated with Okta or NetIQ for single sign-on (SSO) or identity federation, as it may compromise confidentiality and integrity of user accounts and associated resources. The impact extends to sectors with stringent data protection requirements such as finance, healthcare, and government, where identity assurance is paramount. Exploitation could result in data breaches, regulatory non-compliance (e.g., GDPR violations), and operational disruptions. Since the vulnerability does not require user interaction or prior authentication, it can be exploited remotely if the attacker can influence the username attribute. The scope includes all web applications using vulnerable versions of allauth-django with these identity providers, potentially affecting a wide range of organizations across Europe. The absence of known exploits suggests limited current risk but also underscores the need for proactive mitigation to prevent future attacks.

Mitigation Recommendations

European organizations should immediately upgrade allauth-django to version 65.13.0 or later, where the vulnerability is fixed by using the immutable 'sub' claim for user identification. Review and audit all authentication and authorization logic to ensure that mutable attributes like 'preferred_username' are not used for critical security decisions. Implement strict validation and monitoring of identity provider claims to detect anomalous changes in user attributes. Coordinate with Okta and NetIQ administrators to confirm that identity provider configurations enforce immutable user identifiers and that any custom mappings do not revert to using mutable fields. Employ multi-factor authentication (MFA) to add an additional layer of security, reducing the risk of account compromise. Conduct penetration testing and code reviews focused on authentication flows to identify similar weaknesses. Maintain up-to-date threat intelligence to monitor for emerging exploits targeting this vulnerability. Finally, educate development and security teams on the importance of using stable identifiers in identity and access management systems.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-11-18T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 694017f1d9bcdf3f3ddec580

Added to database: 12/15/2025, 2:15:13 PM

Last enriched: 12/15/2025, 2:31:41 PM

Last updated: 12/18/2025, 7:41:50 AM

Views: 18

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats