{"answers":{"affected":"3 open source packages ship an affected version, including social-auth-core.","exploited":"There is no known exploitation of CVE-2026-57179 in the wild and no public exploit code.","fix":"Upgrade social-auth-core to 5.0.0 or later.","what":"CVE-2026-57179 is a medium-severity authentication bypass vulnerability in python-social-auth social-core, published on 24 Sep 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-57179 and fix it if it is affected.\n\nWhat it is: CVE-2026-57179 is a medium-severity authentication bypass vulnerability in python-social-auth social-core, published on 24 Sep 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-57179 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- social-auth-core (PyPI): affected all versions; fixed in 5.0.0\n- social-auth-core (PyPI): affected all versions; fixed in 5.0.0\n- social-auth-core (PyPI): affected all versions; fixed in 5.0.0\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-57179/ (Markdown: https://insights.sbomify.com/CVE-2026-57179/index.md)","id":"CVE-2026-57179","markdown":"https://insights.sbomify.com/CVE-2026-57179/index.md","name":"CVE-2026-57179","record":{"aliases":["DEBIAN-CVE-2026-57179","GHSA-vqg6-3fw6-j9jg","PYSEC-2026-4168","UBUNTU-CVE-2026-57179"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Python social auth library","requires_auth":"none","summary":"Attackers can hijack victim sessions by exploiting unbound partial tokens in resumable authentication flows, leading to unauthorized account access.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"description":"Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the partial-pipeline resume mechanism accepted `partial_token` as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as `mail_validation` or custom steps decorated with `@partial`. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.","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":"social-auth-core has a Session Fixation issue","id":"CVE-2026-57179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Scoold: Forged JWT Accepted as Admin API Token Allowing Unauthorized Access to Sensitive Configuration and Logs","id":"CVE-2026-57183"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":null,"source":"GHSA-vqg6-3fw6-j9jg"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":"pkg:pypi/social-auth-core","source":"GHSA-vqg6-3fw6-j9jg"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":"pkg:pypi/social-auth-core","source":"PYSEC-2026-4168"}],"prev":{"headline":"social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing","id":"CVE-2026-57178"},"products":["social-core"],"published":"2026-09-24","related":[],"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":"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-09-24","vendors":["python-social-auth"]},"summary":"Attackers can hijack victim sessions by exploiting unbound partial tokens in resumable authentication flows, leading to unauthorized account access.","url":"https://insights.sbomify.com/CVE-2026-57179/"}