Python Social Auth is a social authentication/registration mechanism. In versions prior to 5.6.0, upon authentication, the user could be associated by e-mail even if the `associate_by_email` pipeline was not included. This could lead to account compromise when a third-party authentication service does not validate provided e-mail addresses or doesn't require unique e-mail addresses. Version 5.6.0 contains a patch. As a workaround, review the authentication service policy on e-mail addresses; many will not allow exploiting this vulnerability.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 6.3NVD modified 2026-10-08 13:10
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 9
- https://github.com/python-social-auth/social-app-django/commit/10c80e2ebabeccd4e9c84ad0e16e1db74148ed4c
- https://github.com/python-social-auth/social-app-django/issues/220
- https://github.com/python-social-auth/social-app-django/issues/231
- https://github.com/python-social-auth/social-app-django/issues/634
- https://github.com/python-social-auth/social-app-django/pull/803
- https://github.com/python-social-auth/social-app-django/security/advisories/GHSA-wv4w-6qv2-qqfg
- https://github.com/python-social-auth/social-app-django/issues/220
- https://github.com/python-social-auth/social-app-django/issues/231
- https://github.com/python-social-auth/social-app-django/issues/634