CVE-2026-57178: 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 authkey 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 viewerid, accesstoken, apiid, and apiresult, potentially allowing authentication as an arbitrary VK user ID.
Published Sep 24, 2026
Affected packages
social-auth-core
- Ecosystem
- PyPI
- Affected
- < 5.0.0
- Fixed in
- 5.0.0
- Check
pip show social-auth-core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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:
- https://github.com/python-social-auth/social-core/pull/1811
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.
Credited to lalalala5678, nijel.
References
- https://github.com/python-social-auth/social-core/security/advisories/GHSA-3c93-f73f-qc9h
- https://nvd.nist.gov/vuln/detail/CVE-2026-57178
- https://github.com/python-social-auth/social-core/pull/1811
- https://github.com/python-social-auth/social-core/commit/1bfacdd0379e5eb46e169a99ab648b835e9bb6a2
- https://github.com/python-social-auth/social-core/releases/tag/5.0.0
- https://github.com/advisories/GHSA-3c93-f73f-qc9h
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-115910
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
medium6.8Oct 28, 2026CVE-2026-62322
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
medium6.5Oct 15, 2026CVE-2026-57175
social-auth-core has an Improper Authentication issue
medium6.4Sep 24, 2026CVE-2026-57176
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
medium6.8Sep 24, 2026CVE-2026-57177
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
medium4.3Sep 24, 2026CVE-2026-57179
social-auth-core has a Session Fixation issue
medium4.2Sep 24, 2026
