CVE-2026-57176 is a medium-severity (CVSS 6.8) CWE-289 vulnerability in social-auth-core. A fix is available for social-auth-core — see the affected versions and patch details below.
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-57176.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-57176 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
social-auth-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
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:
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:
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | social-auth-core | all versions | 5.0.0pip install --upgrade 'social-auth-core==5.0.0' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for social-auth-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update social-auth-core to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-57176 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability is rated as Moderate severity for Red Hat products because exploitation requires a specific, non-default configuration where the application explicitly authenticates users across multiple distinct Vend shops. In standard deployments of Red Hat Ansible Automation Platform, the Vend OAuth2 backend is…
Disable the Vend OAuth2 authentication backend or restrict integration to a single Vend shop. 1. To disable the feature, ensure the Vend OAuth2 backend is not included in `SOCIAL_AUTH_AUTHENTICATION_BACKENDS` (or `AUTHENTICATION_BACKENDS`) within the application configuration. In standard Red Hat Ansible Automation Platform installations, this backend is disabled by default. 2. If Vend authentication is required, restrict the application configuration to connect to a single trusted Vend shop. Caveats: Removing the backend disables Vend authentication entirely. Restricting to a single store prevents multi-tenant authentication across different shops. Applying configuration changes requires…Source: Red Hat security advisory for CVE-2026-57176 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-57176 in your dependencies?
Find it across PyPI, including transitive dependencies.