CVE-2026-57177: Python2.7 · Python Social Auth is a social authentication/registration mechanism
Affects python2.7Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium.
Data as of 17 Nov 2026, 20:36 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/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 LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. The issue has been fixe in version 5.0.0 by enabling callback state validation for the LoginRadius backend.