How severe is CVE-2026-27982?

No CVSS score has been assigned to CVE-2026-27982 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-27982?

CVE-2026-27982 affects the following packages: django-allauth (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-27982?

Update django-allauth to 65.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27982 is resolved across your whole dependency graph.

How do I detect CVE-2026-27982 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-allauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-27982 if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is CVE-2026-27982 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27982 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27982?

CVE-2026-27982 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-27982?

CVE-2026-27982 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-27982 published, and has it been updated?

CVE-2026-27982 was published on March 5, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-27982 — django-allauth

CVE-2026-27982 is a Open Redirect vulnerability in django-allauth. A fix is available for django-allauth — see the affected versions and patch details below.

django-allauth has an open redirect vulnerability

Also known asGHSA-2jpr-83rg-v67jPYSEC-2026-56

Published

Mar 5, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27982.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs8th percentile — riskier than 8% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍django-allauth

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`django-allauth`	all versions	65.14.1`pip install --upgrade 'django-allauth==65.14.1'`

Affected Products

1 product · 1 configurations

Application

allauthallauth

< 65.14.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for django-allauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update django-allauth to 65.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27982 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

MODERATE: This open redirect vulnerability in django-allauth affects systems where SAML IdP initiated SSO is explicitly enabled. By default, SAML IdP initiated SSO is disabled, which limits the exposure for Red Hat products. Systems with the default configuration are not affected.

Workaround published by Red Hat

To mitigate this vulnerability, ensure that SAML IdP initiated SSO is disabled in django-allauth. This feature is disabled by default, so no action is required if the default configuration has been maintained. If SAML IdP initiated SSO was previously enabled, disable it in your django-allauth configuration.

Source: Red Hat security advisory for CVE-2026-27982 (CC BY 4.0)

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-27982 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works