Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, 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. The issue has been fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.
CVE-2026-57179
This medium-severity CVE scores 4.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.2
- EG Score
- 4.2(low)
- EG Risk
- 23(Track)EG Risk 23/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity42% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 24, 2026
Last Modified
September 24, 2026
Advisory Details (1)
Auto-updated Sep 24, 2026Session Fixation in social-auth-core · Advisory · python-social-auth/social-core · GitHub
https://github.com/python-social-auth/social-core/security/advisories/GHSA-vqg6-3fw6-j9jgVendor Advisories for CVE-2026-57179(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 18:35 UTCEG score recompute
- 2026-09-24 17:37 UTCEG score recompute
- 2026-09-24 17:36 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-57179?
When was CVE-2026-57179 disclosed?
What is the CVSS score of CVE-2026-57179?
How do I remediate CVE-2026-57179?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57179
Is Your Infrastructure Affected by CVE-2026-57179?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.