AllauthApplication
CVE-2026-27982
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn open redirect vulnerability exists in django-allauth versions prior to 65.14.1 when SAML IdP initiated SSO is enabled. Attackers can craft malicious URLs to redirect users to arbitrary external websites, potentially enabling phishing attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
AllauthApplication
< 65.14.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed django-allauth versionRun `pip show django-allauth` or inspect your installed package metadata to find the version numberAffected if The installed version is lower than 65.14.1 (note: version must be checked against the affected range provided)
-
Verify if SAML IdP initiated SSO is enabledInspect your django settings.py or allauth SAML provider configuration for the setting that controls IdP-initiated SSO. This is typically configured through the allauth SAML provider admin interface or via a settings variable that permits IdP-initiated authentication flowsAffected if SAML IdP initiated SSO is explicitly enabled (not left at default disabled state)
-
Confirm SAML provider is configuredCheck if any SAML Identity Provider (IdP) is configured in your allauth installation. Review the allauth SAML provider list in the admin panel or examine settings related to SAML authentication providersAffected if A SAML IdP is configured and active in the allauth setup
-
Review redirect URLs in SAML settingsExamine the allowed assertion consumer service URLs and relay state parameters in your SAML IdP configuration to understand where users could potentially be redirectedAffected if The SAML configuration permits arbitrary or unvalidated redirect URLs
You are affected if django-allauth version is below 65.14.1 AND SAML IdP initiated SSO is enabled in your configuration
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped65.14.1
Upgrade django-allauth to version 65.14.1 or later. If upgrading is not immediately possible, ensure SAML IdP initiated SSO remains disabled (the default) as a compensating control.
65.14.1
- Upgrade django-allauth to version 65.14.1 or later using your package manager (e.g., pip install django-allauth==65.14.1)
- Verify the upgrade was successful by checking the installed version
- If using SAML IdP initiated SSO, verify the configuration is correct and test the redirect behavior to ensure the vulnerability is fixed
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Allauth
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27982 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-27982 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data