{"answers":{"affected":"3 open source packages ship an affected version, including social-auth-core.","exploited":"There is no known exploitation of CVE-2026-57176 in the wild and no public exploit code.","fix":"Upgrade social-auth-core to 5.0.0 or later.","what":"CVE-2026-57176 is a medium-severity authentication bypass vulnerability in python-social-auth social-core, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-57176 and fix it if it is affected.\n\nWhat it is: CVE-2026-57176 is a medium-severity authentication bypass vulnerability in python-social-auth social-core, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-57176 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-57176/ (Markdown: https://insights.sbomify.com/CVE-2026-57176/index.md)","id":"CVE-2026-57176","markdown":"https://insights.sbomify.com/CVE-2026-57176/index.md","name":"CVE-2026-57176","record":{"aliases":["DEBIAN-CVE-2026-57176","GHSA-fp7w-m676-w7gc","PYSEC-2026-4166","UBUNTU-CVE-2026-57176"],"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":"low_privilege","summary":"Attackers can hijack accounts by exploiting user ID collisions across multiple Vend shops in the social-auth-core library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-289","name":"Authentication Bypass by Alternate Name"}],"description":"Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the Vend OAuth2 backend used only the numeric Vend user_id as the social-auth UID. When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. Version 5.0.0 patches the issue.","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 Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend","id":"CVE-2026-57176","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":"social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend","id":"CVE-2026-57177"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":null,"source":"GHSA-fp7w-m676-w7gc"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":"pkg:pypi/social-auth-core","source":"GHSA-fp7w-m676-w7gc"},{"ecosystem":"PyPI","fixed":["5.0.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":"pkg:pypi/social-auth-core","source":"PYSEC-2026-4166"}],"prev":{"headline":"social-auth-core has an Improper Authentication issue","id":"CVE-2026-57175"},"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":"total"},"state":"PUBLISHED","updated":"2026-09-29","vendors":["python-social-auth"]},"summary":"Attackers can hijack accounts by exploiting user ID collisions across multiple Vend shops in the social-auth-core library.","url":"https://insights.sbomify.com/CVE-2026-57176/"}