Authentication Bypass Affecting social-auth-core package, versions <5.0.2-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.22% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIANUNSTABLE-SOCIALAUTHCORE-20153966
  • published26 Sept 2026
  • disclosed24 Sept 2026

Introduced: 24 Sep 2026

CVE-2026-57176  (opens in a new tab)
CWE-289  (opens in a new tab)

How to fix?

Upgrade Debian:unstable social-auth-core to version 5.0.2-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream social-auth-core package and not the social-auth-core package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the Vend OAuth2 backend used only the numeric Vend user_id as the social-auth UID. When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. Version 5.0.0 patches the issue.

CVSS Base Scores

version 3.1