Is django-allauth 65.6 vulnerable?

PyPI · 1 release from 65.6.0 to 65.6.0 · latest django-allauth is 65.22.1 · checked 18 Nov 2026

Yes: 3 known advisories

Yes. django-allauth 65.6.0, the last 65.6 release, is affected by 3 known security advisories (3 medium), including CVE-2026-27982, CVE-2025-65431, CVE-2025-65430. Upgrade to 65.14.1 or later to fix all of them.

Upgrade with:pip install 'django-allauth>=65.14.1'

Is your project on an affected django-allauth?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting django-allauth 65.6.0

  • MediumCVE-2026-27982GHSA-2jpr-83rg-v67j5 Mar 2026

    django-allauth has an open redirect vulnerability

    Affected
    <65.14.1
    Fixed in
    65.14.1
  • MediumCVE-2025-65431GHSA-8m3c-c723-h4p415 Dec 2025

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

    Affected
    <65.13.0
    Fixed in
    65.13.0
  • MediumCVE-2025-65430GHSA-qhmc-3mvr-f2j415 Dec 2025

    django-allauth does not reject access tokens for inactive users

    Affected
    <65.13.0
    Fixed in
    65.13.0

Which of your client projects are still on django-allauth 65.6?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact django-allauth version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other django-allauth versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.