Quick answers
- Is CVE-2026-27982 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-27982 being exploited in the wild.
- How severe is CVE-2026-27982?
- Medium severity, with a CVSS score of 4.3, published 5 March 2026.
- Which products and versions are affected?
- Pennersr Allauth < 65.14.1; django-allauth (PyPI) < 65.14.1, ECOSYSTEM:introduced=0,fixed=65.14.1.
- Is there a fix for CVE-2026-27982?
- Yes. django-allauth (PyPI): upgrade to 65.14.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-27982 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-27982?
- Check whether you run Pennersr Allauth or django-allauth (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- django-allauth (PyPI): upgrade to 65.14.1 or later
pip install "django-allauth>=65.14.1"
Technical details
An open redirect vulnerability (CWE-601) exists in django-allauth when SAML IdP-initiated Single Sign-On (SSO) is enabled. The vulnerability stems from the application's failure to validate the 'RelayState' parameter in SAML requests, which is used to determine the destination URL after a successful login. A remote, unauthenticated attacker can craft a URL containing a malicious external site in the RelayState parameter; if a user clicks this link and authenticates, they will be redirected to the attacker-controlled domain. This issue is patched in version 65.14.1. Note that SAML IdP-initiated SSO is disabled by default in standard configurations.
Affected products
- allauth django-allauth < 65.14.1
Identifiers
- CVE-2026-27982
- GHSA-2jpr-83rg-v67j
- PYSEC-2026-56
Timeline
- 2026-02-07: patched: Version 65.14.1 released
- 2026-03-05: disclosed: Initial public disclosure and CVE assignment