CVE-2026-57176: social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
Impact The Vend OAuth2 backend used only the numeric Vend userid 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.
Published Sep 24, 2026
Affected packages
social-auth-core
- Ecosystem
- PyPI
- Affected
- < 5.0.0
- Fixed in
- 5.0.0
- Check
pip show social-auth-core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Patches
The issue has been fixed by scoping Vend social-auth UIDs by shop.
Users should upgrade to a patched version.
Fix:
- https://github.com/python-social-auth/social-core/pull/1795
Workarounds
Applications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop.
If Vend authentication is not required, the Vend backend can also be disabled by removing it from SOCIAL_AUTH_AUTHENTICATION_BACKENDS.
There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
- https://lzhou1110.github.io/
- https://zyy0530.github.io/
- https://str1ckl4nd.github.io/
- https://maurice.busystar.org/
- https://7thparkk.github.io/
Credited to mauriceng98, nijel.
References
- https://github.com/python-social-auth/social-core/security/advisories/GHSA-fp7w-m676-w7gc
- https://nvd.nist.gov/vuln/detail/CVE-2026-57176
- https://github.com/python-social-auth/social-core/pull/1795
- https://github.com/python-social-auth/social-core/commit/dee7ad1785877afd355dd6860598823d2631b76e
- https://github.com/python-social-auth/social-core/releases/tag/5.0.0
- https://github.com/advisories/GHSA-fp7w-m676-w7gc
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-115910
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
medium6.8Oct 28, 2026CVE-2026-62322
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
medium6.5Oct 15, 2026CVE-2026-57175
social-auth-core has an Improper Authentication issue
medium6.4Sep 24, 2026CVE-2026-57177
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
medium4.3Sep 24, 2026CVE-2026-57178
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
high7.4Sep 24, 2026CVE-2026-57179
social-auth-core has a Session Fixation issue
medium4.2Sep 24, 2026
