CVE-2026-57179: social-auth-core has a Session Fixation issue
Impact The partial-pipeline resume mechanism accepted partialtoken as a bearer credential without binding it to the browser session that created it. Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow.
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 partial-pipeline resume mechanism accepted partial_token as a bearer credential without binding it to the browser session that created it.
Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account.
The issue affects applications using partial pipeline steps such as mail_validation or custom steps decorated with @partial.
Patches
The issue has been fixed by binding partial pipeline resumes to the originating browser session.
Users should upgrade to a patched version.
Fix:
- https://github.com/python-social-auth/social-core/pull/1816
- https://github.com/python-social-auth/social-docs/pull/444
- https://github.com/python-social-auth/social-app-django/pull/1009
Workarounds
Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including mail_validation and custom steps decorated with @partial.
If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.
There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.
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-vqg6-3fw6-j9jg
- https://nvd.nist.gov/vuln/detail/CVE-2026-57179
- https://github.com/python-social-auth/social-core/pull/1816
- https://github.com/python-social-auth/social-core/commit/0418782454ac7bbc6a9230ea21f7f5066fe89686
- https://github.com/python-social-auth/social-core/releases/tag/5.0.0
- https://github.com/advisories/GHSA-vqg6-3fw6-j9jg
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-57175
social-auth-core has an Improper Authentication issue
medium6.4Sep 24, 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, 2026
