Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-57176 Overview
CVE-2026-57176 is an authentication vulnerability in Python Social Auth, a widely used social authentication and registration library. The flaw affects the Vend OAuth2 backend in versions prior to 5.0.0. The backend used only the numeric Vend user_id as the social-auth UID, ignoring the shop context. When multiple Vend shops authenticated through the same application, users from different shops sharing the same internal Vend user ID collided in the social-auth association table. An attacker from one shop could be authenticated as a local account previously associated with the same numeric user ID from another shop. Version 5.0.0 patches the issue.
Critical Impact
Cross-tenant account takeover between distinct Vend shops authenticating through the same Python Social Auth application.
Affected Products
- Python Social Auth social-core versions prior to 5.0.0
- Applications using the Vend OAuth2 backend
- Deployments integrating more than one Vend shop with a single application
Discovery Timeline
- 2026-09-24 - CVE-2026-57176 published to NVD
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-57176
Vulnerability Analysis
The Vend OAuth2 backend in social-core generated the social-auth UID using only the numeric Vend user_id field. The social-auth association table stores a (provider, uid) tuple that maps external identities to local accounts. Because the shop identifier was omitted from the UID, two authenticated users originating from different Vend shops could resolve to the same association record. The library then returned the local account previously linked to that UID, authenticating the second user as the first.
The issue is categorized under CWE-289: Authentication Bypass by Alternate Name. The vulnerability affects only applications that connect more than one Vend shop through a shared Python Social Auth instance. Single-shop deployments are not impacted.
Root Cause
The root cause is insufficient scoping of the external identifier used for identity federation. Vend user_id values are unique within a shop but not globally unique across shops. The backend treated them as if they were globally unique. The fix in version 5.0.0 combines the shop identifier with the numeric user ID so each UID is unique across tenants.
Attack Vector
Exploitation requires an attacker to control or register a Vend account in a shop that is federated to the same application as the victim. The attacker must know, or be assigned, a Vend user_id matching the victim's internal ID in another shop. The attacker then authenticates through the Vend OAuth2 flow. Python Social Auth looks up the UID in the association table and returns the victim's local account.
No exploit code is publicly available for this issue. Refer to the GitHub Security Advisory GHSA-fp7w-m676-w7gc for additional details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-57176
Indicators of Compromise
- Social-auth association records where the same uid value is linked to multiple distinct local user accounts over time
- Successful OAuth2 logins to a local account from a Vend shop different from the one originally associated with it
- Unexpected session establishment for accounts following a Vend OAuth2 callback
Detection Strategies
- Audit the social_auth_usersocialauth table for Vend-provider rows where numeric UIDs appear across different associated user accounts
- Correlate OAuth2 callback events with the originating shop domain and compare against the shop associated at account creation
- Review application authentication logs for logins where the Vend shop subdomain or hostname changes for a given social-auth UID
Monitoring Recommendations
- Enable detailed logging of social-auth pipeline steps, including associate_user and associate_by_email
- Alert when a Vend OAuth2 login resolves to a local account previously bound to a different shop context
- Track upgrades of the social-core dependency across environments to confirm the patched version is deployed
How to Mitigate CVE-2026-57176
Immediate Actions Required
- Upgrade social-core to version 5.0.0 or later in all applications using the Vend OAuth2 backend
- Inventory all deployments that federate more than one Vend shop through a shared Python Social Auth instance
- Audit the social-auth association table for duplicate or ambiguous Vend UID mappings and remediate affected accounts
Patch Information
The maintainers released version 5.0.0 of social-core, which scopes the Vend OAuth2 UID using both the shop identifier and the numeric user ID. See the GitHub Security Advisory GHSA-fp7w-m676-w7gc for the full advisory and commit references.
Workarounds
- Restrict the application to a single Vend shop until the upgrade is applied
- Implement a custom pipeline step that augments the Vend UID with the shop identifier before association lookup
- Invalidate existing Vend-backend social-auth associations and require re-authentication after patching
# Upgrade social-core to the patched release
pip install --upgrade 'social-auth-core>=5.0.0'
# Verify installed version
pip show social-auth-core | grep -i version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

