CVE-2026-57175 is a medium-severity (CVSS 6.4) Improper Authentication vulnerability in social-auth-core. A fix is available for social-auth-core — see the affected versions and patch details below.
social-auth-core has an Improper Authentication issue
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-57175.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-57175 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 SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued AuthnRequest.
Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker's SAML identity to a logged-in victim's local account. The attacker could then authenticate through SAML and gain access to the victim's account.
The issue affects applications using the SAML backend together with authenticated account association.
Patches
The issue has been fixed by validating SAML responses against stored AuthnRequest IDs.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.
If SAML login is not required, the SAML backend can also be disabled by removing it from SOCIAL_AUTH_AUTHENTICATION_BACKENDS.
There is no complete workaround while continuing to allow vulnerable SAML account association.
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-57175 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
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 impact for Red Hat products because exploitation requires specific non-default conditions, including an active SAML backend configured for account association alongside user interaction with an authenticated session. Additionally, an attacker must already possess valid…
Disable the SAML authentication backend if it is not required for your deployment. In Red Hat Ansible Automation Platform, ensure SAML authentication is disabled in Automation Controller settings (under Settings > SAML settings) and rely on alternative authentication mechanisms such as LDAP or local accounts. In custom applications utilizing python-social-auth, remove the SAML backend from `SOCIAL_AUTH_AUTHENTICATION_BACKENDS` or disable SAML account linking for authenticated sessions. Caveats: Disabling SAML authentication prevents users from authenticating or associating accounts through SAML Identity Providers.Source: Red Hat security advisory for CVE-2026-57175 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2026-57175 in your dependencies?
Find it across PyPI, including transitive dependencies.