CVE-2026-57179: social-auth-core has a Session Fixation issue
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.
References
- github.com/advisories/GHSA-vqg6-3fw6-j9jg
- github.com/python-social-auth/social-core/commit/0418782454ac7bbc6a9230ea21f7f5066fe89686
- github.com/python-social-auth/social-core/pull/1816
- github.com/python-social-auth/social-core/releases/tag/5.0.0
- github.com/python-social-auth/social-core/security/advisories/GHSA-vqg6-3fw6-j9jg
- nvd.nist.gov/vuln/detail/CVE-2026-57179
Code Behaviors & Features
Detect and mitigate CVE-2026-57179 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →