CVE-2026-57176— social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
Quick assessment
Affected
python-social-auth social-core
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Python Social Auth 是一种社会化认证/注册机制。在 5.0.0 版本之前，Vend OAuth2 后端仅使用数字形式的 Vend 用户 ID 作为 social-auth 的唯一标识符（UID）。当多个 Vend 商店通过同一应用程序进行认证时，来自不同商店但具有相同内部 Vend 用户 ID 的用户，可能会在 social-auth 关联表中发生 ID 冲突。这可能导致一个商店中的用户被错误地认证为另一个商店中先前与该数字用户 ID 关联的本地账户。该问题影响使用 Vend OAuth2 后端并
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2026-57176
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
使用候选名称进行的认证绕过
Source: CVE Program / CVE List V5
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| python-social-auth | social-core | < 5.0.0 | - |
|
II. Public POCs for CVE-2026-57176
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2026-57176
请登录查看更多情报信息。
Vendor Advisories for CVE-2026-57176 (1)
Same Patch Batch · python-social-auth · 2026-09-24 · 5 CVEs total
| CVE-2026-57178 | 7.4 HIGH | social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing |
| CVE-2026-57175 | 6.4 MEDIUM | social-auth-core has an Improper Authentication issue |
| CVE-2026-57177 | 4.3 MEDIUM | social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend |
| CVE-2026-57179 | 4.2 MEDIUM | social-auth-core has a Session Fixation issue |
IV. Related Vulnerabilities
Same product: social-core
Same vendor: python-social-auth
-
CVE-2026-57179
social-auth-core has a Session Fixation issue -
CVE-2026-57178
social-auth-core: VK App backend accepts unsigned callback d -
CVE-2026-57177
social-auth-core has Login CSRF via Missing State Parameter -
CVE-2026-57175
social-auth-core has an Improper Authentication issue -
CVE-2025-61783
Python Social Auth - Django has unsafe account association
Same weakness: CWE-289
-
CVE-2026-95514
WordPress Netgsm plugin <= 2.10.0 - Bypass Vulnerability vul -
CVE-2026-76183
Apache Tomcat: Bypass of security constraints for WebSocket -
CVE-2026-73511
Envoy: Potential path-matching/authentication bypass when us -
CVE-2026-92579
AVideo through 29.0 Broken Access Control via CSRF Exemption -
CVE-2026-12101
Security vulnerabilities have been addressed in IBM Verify I
V. Comments for CVE-2026-57176
No comments yet