social-auth-core
Affected
- introduced
0, fixed5.0.0(ecosystem)
Fixed versions
5.0.0
Fix
- Fixed version
5.0.0pip install --upgrade social-auth-core==5.0.0
Advisory
Also known as: CVE-2026-57178, GHSA-3c93-f73f-qc9h
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
Impact
The vk-app backend accepted VK application callback data without verifying the callback signature when the auth_key parameter was omitted.
Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as viewer_id, access_token, api_id, and api_result, potentially allowing authentication as an arbitrary VK user ID.
The issue affects only applications using the vk-app backend.
Patches
The issue has been fixed by requiring auth_key to be present and valid before callback data is trusted.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable the vk-app backend by removing social_core.backends.vk.VKAppOAuth2 from SOCIAL_AUTH_AUTHENTICATION_BACKENDS.
There is no complete workaround while continuing to use the vulnerable backend.
Credits
Reported by @lalalala5678 through GitHub private vulnerability reporting.
High Basis: CVSS v3 score 7.4, vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
0, fixed 5.0.0 (ecosystem)5.0.0
5.0.0pip install --upgrade social-auth-core==5.0.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0