CVE-2026-57175: Python2.7 · Python Social Auth is a social authentication/registration mechanism
Affects python2.7Source GCVE Database
Not known to be exploited · CVSS 6.4 Medium · fixed in 5.0.0 : update python2.7 when convenient.
Data as of 17 Nov 2026, 20:36 UTC
- Patch
- Available – fixed in 5.0.0
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 24 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10python3.14pkg:deb/ubuntu/python3.14?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSpython3.12pkg:deb/ubuntu/python3.12?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSpython3.10pkg:deb/ubuntu/python3.10?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSpython2.7pkg:deb/ubuntu/python2.7?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSpython3.11pkg:deb/ubuntu/python3.11?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSpython3.8pkg:deb/ubuntu/python3.8?arch=source&distro=esm-infra/focalOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`. Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker's SAML identity to a logged-in victim's local account. The attacker could then authenticate through SAML and gain access to the victim's account. The issue affects applications using the SAML backend together with authenticated account association. The issue has been fixed in version 5.0.0 by validating SAML responses against stored `AuthnRequest` IDs.