CVE-2026-57178: python-social-auth social-core · Improper Authentication
Affects python-social-auth social-coreSource CVE Database V5
Not known to be exploited · CVSS 7.4 High : upgrade to 5.0.0 soon.
Data as of 7 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% 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:N/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 8 Nov 2026.
What to do
Upgrade python-social-auth social-core to 5.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| python-social-authsocial-core | Affected
| Fixed in
|
PyPIsocial-corepkg:pypi/social-coreOther threats | Affected
| Fixed in
|
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 vulnerability is fixed by enforcing the presence and validity of the auth_key parameter before trusting VK callback data. Applications using the vk-app backend should not accept callback data without proper signature verification. No other mitigations are indicated.
Description
Python Social Auth's social-core component prior to version 5.0.0 contains an improper authentication vulnerability in the vk-app backend. The backend accepted VK application callback data without verifying the callback signature if the auth_key parameter was missing. This allowed attackers to impersonate arbitrary VK user identities by manipulating callback fields. The issue is fixed in version 5.0.0 by enforcing the presence and validity of auth_key before trusting callback data.