Skip to main content
VulnerabilityPublished

CVE-2026-57179: python-social-auth social-core · Session Fixation

Affects python-social-auth social-coreSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.2 Medium : upgrade to 5.0.0 when convenient.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
4.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.0.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade python-social-auth social-core to 5.0.0.

Affected software

ProductAffectedFixed in
python-social-authsocial-coreAffected
  • <5.0.0
Fixed in
  • 5.0.0
PyPIsocial-corepkg:pypi/social-coreOther threatsAffected
  • <5.0.0
Fixed in
  • 5.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade python-social-auth social-core to version 5.0.0 or later, where the partial pipeline resume mechanism is bound to the originating browser session, effectively mitigating the session fixation vulnerability. No other mitigation is indicated or required.

Description

CVE-2026-57179 is a session fixation vulnerability in python-social-auth's social-core component affecting versions prior to 5.0.0. The issue arises because the partial-pipeline resume mechanism accepted a partial token as a bearer credential without binding it to the originating browser session. This flaw could allow an attacker to initiate an authentication flow, obtain a valid partial token, and trick a victim's browser into resuming the attacker's authentication flow, effectively authenticating the victim as the attacker. The vulnerability affects applications using partial pipeline steps such as mail_validation or custom steps decorated with @partial. The issue was fixed in version 5.0.0 by binding partial pipeline resumes to the originating browser session.

References

Community reviews

Loading reviews…