Description
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.
Published: 2026-09-24
Score: 7.4 High
EPSS: < 1% Very Low
KEV: No
Impact: Authentication Bypass
Action: Immediate Patch
AI Analysis

Impact

A flaw in the VK application backend of the python-social-auth social-core library allows an attacker to supply unsigned callback data when the auth_key parameter is omitted. The backend then accepts this data as a verified VK identity. This results in an authentication bypass, enabling the attacker to impersonate an arbitrary VK user and obtain fields such as viewer_id, access_token, api_id, and api_result. The weakness is defined by CWE‑287 (Improper Authentication) and CWE‑347 (Missing or Incorrect Signature Verification).

Affected Systems

The issue affects any application that uses the vk‑app backend provided by the python-social-auth:social-core package. Versions earlier than 5.0.0 are vulnerable; starting with 5.0.0 the backend requires a valid auth_key before any callback data is trusted.

Risk and Exploitability

The CVSS score is 7.4, indicating a high severity due to the potential for unauthorized access. The EPSS score is not available, and the vulnerability is not listed in CISA KEV, suggesting no publicly known exploits yet. Attackers can exploit the flaw remotely by constructing a malicious VK callback and directing the application to process it when auth_key is missing. The vulnerability’s impact is limited to authentication, but the compromised credentials could allow further actions within the application.

Generated by OpenCVE AI on September 25, 2026 at 05:05 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the official update to python-social-auth social-core version 5.0.0 or later to enforce auth_key validation on VK callbacks.
  • Verify that the auth_key is present in your configuration and that the backend validates it before trusting any callback data.
  • If an upgrade cannot be performed immediately, disable the vk‑app backend or enforce manual signature checks to reject callbacks lacking a valid auth_key.

Generated by OpenCVE AI on September 25, 2026 at 05:05 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-3c93-f73f-qc9h social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
History

Fri, 25 Sep 2026 14:45:00 +0000

Type Values Removed Values Added
First Time appeared Python-social-auth
Python-social-auth social-core
Vendors & Products Python-social-auth
Python-social-auth social-core

Fri, 25 Sep 2026 12:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

threat_severity

Important


Thu, 24 Sep 2026 17:30:00 +0000

Type Values Removed Values Added
Description 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.
Title social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
Weaknesses CWE-287
CWE-347
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N'}


Subscriptions

Python-social-auth Social-core
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-24T17:25:47.225Z

Reserved: 2026-06-24T01:47:55.286Z

Link: CVE-2026-57178

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-24T18:17:14.970

Modified: 2026-09-25T13:27:31.790

Link: CVE-2026-57178

cve-icon Redhat

Severity : Important

Publid Date: 2026-09-24T17:25:47Z

Links: CVE-2026-57178 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-09-25T14:16:46Z

Weaknesses
  • CWE-287

    Improper Authentication

  • CWE-347

    Improper Verification of Cryptographic Signature