VulnerabilityPublished 5 Mar 2026Updated 6 Mar 2026

CVE-2026-27982: django-allauth · Open Redirect

Affects django-allauthSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 65.14.1 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 65.14.1

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade django-allauth to 65.14.1.

Affected software

Product	Affected	Fixed in
allauthdjango-allauth	Affected =prior to 65.14.1	Fixed in–
PyPIdjango-allauth`pkg:pypi/django-allauth`Other threats	Affected <65.14.1	Fixed in 65.14.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should upgrade django-allauth to version 65.14.1 or later, where the open redirect issue has been fixed. If immediate upgrading is not feasible, administrators should disable the SAML IdP initiated SSO feature until a patch can be applied, as it is disabled by default and only enabled explicitly. Additionally, implement strict validation of redirect URLs to ensure they point only to trusted internal domains. Web application firewalls (WAFs) can be configured to detect and block suspicious redirect parameters. Educate users to be cautious of unexpected redirects and to verify URLs before clicking. Monitoring logs for unusual redirect patterns can help detect exploitation attempts. Finally, consider employing multi-factor authentication (MFA) to reduce the impact of credential theft resulting from phishing.

Description

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.

Impact

The primary impact of this vulnerability is the potential for phishing and social engineering attacks. By exploiting the open redirect, attackers can lure users into visiting malicious websites that appear trustworthy, potentially leading to credential theft, malware infection, or further exploitation. While the vulnerability does not directly expose sensitive data or disrupt service availability, it undermines the integrity of the authentication process and user trust. Organizations relying on django-allauth with SAML IdP initiated SSO enabled may face reputational damage and increased risk of user compromise. The scope is limited to applications that have explicitly enabled this SAML feature, which is not enabled by default, reducing the overall exposure. However, given the widespread use of Django and django-allauth in web applications globally, the risk remains significant for affected deployments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Mar 2026, 20:23 UTC

Technical details

References

Community reviews

Related threats