Findings

CVE-2025-65431

An issue was discovered in allauth-django before 65.13.0.

Published Dec 15, 2025 · updated Oct 14, 2026 · allauth allauth

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.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Dec 15, 2025 · NIST NVD

    Detected

    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.

  2. Oct 14, 2026 · NIST NVD

    Updated

    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.

Affected

  • cpe allauth/allauthversion unspecified

Sources

  • CVE.orgVulnerability recordCVE-2025-65431

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-65431

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-2025-65431

    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

    nvd.nist.gov

References