CVE-2026-57175: social-auth-core has an Improper Authentication issue
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.
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 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:
- https://github.com/python-social-auth/social-core/pull/1794
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:
- 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-vq6g-g6c7-5f2j
- https://nvd.nist.gov/vuln/detail/CVE-2026-57175
- https://github.com/python-social-auth/social-core/pull/1794
- https://github.com/python-social-auth/social-core/commit/5c72f71125bc60e4411f09e2a9f998de5da7fcb6
- https://github.com/python-social-auth/social-core/releases/tag/5.0.0
- https://github.com/advisories/GHSA-vq6g-g6c7-5f2j
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-57176
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
medium6.8Sep 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
