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/22/2025, 14:34:00 UTC

Technical Analysis

CVE-2025-65431 is a vulnerability discovered in the allauth-django authentication library before version 65.13.0. The issue arises because the library used the 'preferred_username' attribute from third-party identity providers such as Okta and NetIQ as the primary identifier for user accounts. However, 'preferred_username' is a mutable attribute, meaning it can be changed by the user or an attacker with access to the identity provider, which undermines its reliability for authorization decisions. This can lead to security issues such as impersonation or unauthorized privilege escalation if an attacker changes their 'preferred_username' to that of another user. The correct approach, now implemented in the patched versions, is to use the 'sub' attribute, which is a unique and immutable identifier assigned by the identity provider and is stable for authorization purposes. The vulnerability is classified under CWE-287 (Improper Authentication) and has a CVSS v3.1 base score of 5.4, indicating a medium severity level. The attack vector is network-based (AV:N), with low attack complexity (AC:L), requiring privileges (PR:L) but no user interaction (UI:N). The impact affects confidentiality and integrity but not availability. No known exploits have been reported in the wild as of the publication date. This vulnerability primarily affects applications that integrate allauth-django with Okta or NetIQ for authentication and authorization workflows, especially where authorization decisions rely on user identifiers.

Potential Impact

For European organizations, the impact of CVE-2025-65431 can be significant in environments where allauth-django is used as part of the authentication stack with Okta or NetIQ identity providers. If exploited, attackers could manipulate the 'preferred_username' attribute to impersonate other users or escalate privileges, potentially gaining unauthorized access to sensitive data or systems. This could lead to breaches of personal data, intellectual property theft, or disruption of business operations. Given the GDPR regulatory environment in Europe, unauthorized access incidents could result in regulatory penalties and reputational damage. Organizations relying on these identity providers for single sign-on (SSO) or federated authentication are particularly at risk. The vulnerability does not affect availability but compromises confidentiality and integrity, which are critical for maintaining trust and compliance. Since exploitation requires some level of privileges, insider threats or compromised accounts could be leveraged to exploit this vulnerability, increasing the risk in environments with insufficient privilege management.

Mitigation Recommendations

European organizations should immediately upgrade allauth-django to version 65.13.0 or later, where the vulnerability is fixed by switching from 'preferred_username' to the immutable 'sub' attribute for user identification. Additionally, organizations should audit their authentication and authorization logic to ensure no reliance on mutable attributes for critical security decisions. Implement strict privilege management and monitoring to detect any anomalous changes in user attributes or suspicious authentication behavior. Where possible, enforce multi-factor authentication (MFA) to reduce the risk of account compromise that could lead to exploitation. Regularly review and update identity provider configurations to ensure compliance with best practices for attribute usage. Conduct penetration testing and code reviews focusing on authentication flows to identify similar weaknesses. Finally, maintain up-to-date inventories of software dependencies and apply security patches promptly to reduce exposure time.

Need more detailed analysis?Upgrade to Pro Console

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/22/2025, 2:34:00 PM

Last updated: 2/6/2026, 7:18:38 AM

Views: 51

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats