Vulnerability in social-auth-core (CVE-2026-57179)
Summary
Vulnerability in social-auth-core (CVE-2026-57179). Risk of unauthorized operations or information disclosure. Exploitable via partial_token. Mitigation: upgrade to 5.0.0 or later.
Original description
The description as published by the source.
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,…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-57179 has been found in social-auth-core.
Attackers can target a specific entry point like partial_token over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.2/10.
What to do: upgrade social-auth-core to 5.0.0 or later.
If unsure, ask your IT team or search "social-auth-core CVE-2026-57179" on the vendor's site.
CVE-2026-57179 (social-auth-core) — CWE-384 / CVSS v3 4.2
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: partial_token / mail_validation
Patched: 5.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-384) exists in social-auth-core. Attackers reach the vulnerable code path via partial_token without authentication.
Check the vendor advisory for the affected versions of social-auth-core. Attack surface: partial_token / mail_validation.
Severity: Medium (CVSS 4.2/10). Risk of unauthorized operations or information disclosure.
Update to 5.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'social-auth-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'social-auth-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
social-auth-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade social-auth-core to 5.0.0ステージング環境で 5.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web nvd.nist.gov
- web github.com
- web github.com
- web github.com
- web github.com