{"answers":{"affected":"3 open source packages ship an affected version, including django-allauth. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27982 in the wild and no public exploit code.","fix":"Upgrade django-allauth to 65.14.1 or later.","what":"CVE-2026-27982 is a medium-severity vulnerability in django-allauth, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27982 and fix it if it is affected.\n\nWhat it is: CVE-2026-27982 is a medium-severity vulnerability in django-allauth, published on 5 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-27982 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- django-allauth (PyPI): affected all versions; fixed in 65.14.1\n- django-allauth (PyPI): affected all versions; fixed in 65.14.1\n- django-allauth (PyPI): affected all versions; fixed in 65.14.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-27982/ (Markdown: https://insights.sbomify.com/CVE-2026-27982/index.md)","id":"CVE-2026-27982","markdown":"https://insights.sbomify.com/CVE-2026-27982/index.md","name":"CVE-2026-27982","record":{"aliases":["DEBIAN-CVE-2026-27982","GHSA-2jpr-83rg-v67j","PYSEC-2026-56","UBUNTU-CVE-2026-27982"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Django authentication library","requires_auth":"none","summary":"Attackers can redirect users to malicious sites via crafted URLs when SAML IdP initiated SSO is enabled in django-allauth.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"jpcert","cpe":[{"product":"allauth","vendor":"allauth"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"django-allauth has an open redirect vulnerability","id":"CVE-2026-27982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"open_redirect","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"WordPress LMS Elementor Pro plugin \u003c= 1.0.4 - Privilege Escalation vulnerability","id":"CVE-2026-27983"},"packages":[{"ecosystem":"PyPI","fixed":["65.14.1"],"introduced":["0"],"last_affected":[],"package":"django-allauth","purl":null,"source":"GHSA-2jpr-83rg-v67j"},{"ecosystem":"PyPI","fixed":["65.14.1"],"introduced":["0"],"last_affected":[],"package":"django-allauth","purl":"pkg:pypi/django-allauth","source":"GHSA-2jpr-83rg-v67j"},{"ecosystem":"PyPI","fixed":["65.14.1"],"introduced":["0"],"last_affected":[],"package":"django-allauth","purl":"pkg:pypi/django-allauth","source":"PYSEC-2026-56"}],"prev":{"headline":"HomeBox has an Auth Rate Limit Bypass via IP Spoofing","id":"CVE-2026-27981"},"products":["django-allauth"],"published":"2026-03-05","related":[{"cvss_score":5.4,"headline":"django-allauth does not reject access tokens for inactive users","id":"CVE-2025-65430","kev_date_added":null,"published":"2025-12-15"},{"cvss_score":5.4,"headline":"django-allauth's Okta and NetIQ implementations used a mutable identifier for authorization decisions","id":"CVE-2025-65431","kev_date_added":null,"published":"2025-12-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-06","vendors":["allauth"]},"summary":"Attackers can redirect users to malicious sites via crafted URLs when SAML IdP initiated SSO is enabled in django-allauth.","url":"https://insights.sbomify.com/CVE-2026-27982/"}