Skip to content

← Public intelligence

PyPI package

django-allauth

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.1PyPIAmendedPublished

    django-allauth has an open redirect vulnerability

    CVE-2026-27982 · GHSA-2jpr-83rg-v67j

    Affected
    • PyPI django-allauth < 65.14.1
    Fixed in
    65.14.1· Vendor fix available
    Issue
    An open redirect vulnerability exists in django-allauth versions prior to 65.14.1 when SAML IdP initiated SSO is enabled (it is disabled by default), which may allow an attacker to redirect users to an arbitrary external website via a crafted URL.

    Recommended action: Upgrade to 65.14.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. Medium, CVSS 5.4PyPIAmendedPublished

    django-allauth's Okta and NetIQ implementations used a mutable identifier for authorization decisions

    CVE-2025-65431 · GHSA-8m3c-c723-h4p4

    Affected
    • PyPI django-allauth < 65.13.0
    Fixed in
    65.13.0· Vendor fix available
    Issue
    An issue was discovered in allauth-django before 65.13.0. Both Okta and NetIQ were using preferredusername 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.

    Recommended action: Upgrade to 65.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  3. Medium, CVSS 5.4PyPIAmendedPublished

    django-allauth does not reject access tokens for inactive users

    CVE-2025-65430 · GHSA-qhmc-3mvr-f2j4

    Affected
    • PyPI django-allauth < 65.13.0
    Fixed in
    65.13.0· Vendor fix available
    Issue
    An issue was discovered in allauth-django before 65.13.0. IdP: marking a user as isactive=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.

    Recommended action: Upgrade to 65.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →