https://vulnerability.circl.lu/rss/recent/all/10 Most recent entries from all 2026-10-01T06:14:26.849864+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent entries. https://vulnerability.circl.lu/vuln/fkie_cve-2026-57178 fkie_cve-2026-57178 2026-10-01T06:14:31.036074+00:00

Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, 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. The issue has been fixed in version 5.0.0 by requiring `auth_key` to be present and valid before callback data is trusted.

 https://vulnerability.circl.lu/vuln/ghsa-3c93-f73f-qc9h GHSA-3c93-f73f-qc9h — social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing 2026-10-01T06:14:31.036168+00:00

Affected: PyPI: social-auth-core

### 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.

 https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-57178 UBUNTU-CVE-2026-57178 2026-10-01T06:14:31.036250+00:00

Affected: Ubuntu:Pro:14.04:LTS: python2.7, Ubuntu:Pro:14.04:LTS: python3.4, Ubuntu:Pro:14.04:LTS: python3.5, Ubuntu:Pro:16.04:LTS: python2.7, Ubuntu:Pro:16.04:LTS: python3.5, Ubuntu:Pro:18.04:LTS: python2.7, Ubuntu:Pro:18.04:LTS: python3.6, Ubuntu:Pro:18.04:LTS: python3.7, Ubuntu:Pro:18.04:LTS: python3.8, Ubuntu:Pro:20.04:LTS: python3.8 and 7 more

Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, 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. The issue has been fixed in version 5.0.0 by requiring `auth_key` to be present and valid before callback data is trusted.