Repository navigation
chore(deps): update dependency social-auth-core to v6 [security] - #861
Merged
Merged
Conversation
renovate
Bot
deleted the
renovate/pypi-social-auth-core-vulnerability
branch
November 11, 2026 07:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
4.8.7→6.2.0social-auth-core has an Improper Authentication issue
CVE-2026-57175 / GHSA-vq6g-g6c7-5f2j
More information
Details
Impact
The SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued
AuthnRequest.Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker's SAML identity to a logged-in victim's local account. The attacker could then authenticate through SAML and gain access to the victim's account.
The issue affects applications using the SAML backend together with authenticated account association.
Patches
The issue has been fixed by validating SAML responses against stored
AuthnRequestIDs.Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.
If SAML login is not required, the SAML backend can also be disabled by removing it from
SOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to allow vulnerable SAML account association.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
CVE-2026-57176 / GHSA-fp7w-m676-w7gc
More information
Details
Impact
The Vend OAuth2 backend used only the numeric Vend
user_idas 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.
Patches
The issue has been fixed by scoping Vend social-auth UIDs by shop.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop.
If Vend authentication is not required, the Vend backend can also be disabled by removing it from
SOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
CVE-2026-57177 / GHSA-x7qq-23vw-7pfg
More information
Details
Impact
The LoginRadius backend did not validate OAuth state during the authentication flow.
Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity.
The issue affects only applications using the LoginRadius backend.
Patches
The issue has been fixed by enabling callback state validation for the LoginRadius backend.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable the LoginRadius backend by removing it from
SOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to use the vulnerable backend.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
CVE-2026-57178 / GHSA-3c93-f73f-qc9h
More information
Details
Impact
The
vk-appbackend accepted VK application callback data without verifying the callback signature when theauth_keyparameter 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, andapi_result, potentially allowing authentication as an arbitrary VK user ID.The issue affects only applications using the
vk-appbackend.Patches
The issue has been fixed by requiring
auth_keyto be present and valid before callback data is trusted.Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable the
vk-appbackend by removingsocial_core.backends.vk.VKAppOAuth2fromSOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to use the vulnerable backend.
Credits
Reported by @lalalala5678 through GitHub private vulnerability reporting.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
social-auth-core has a Session Fixation issue
CVE-2026-57179 / GHSA-vqg6-3fw6-j9jg
More information
Details
Impact
The partial-pipeline resume mechanism accepted
partial_tokenas a bearer credential without binding it to the browser session that created it.Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account.
The issue affects applications using partial pipeline steps such as
mail_validationor custom steps decorated with@partial.Patches
The issue has been fixed by binding partial pipeline resumes to the originating browser session.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including
mail_validationand custom steps decorated with@partial.If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.
There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
CVE-2026-62322 / GHSA-526j-582w-7fm9
More information
Details
Impact
Applications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account.
If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path.
Patches
Workarounds
Only applications that enable the LINE backend are affected.
Credits
Thanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub.
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
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
CVE-2026-115910 / GHSA-h2r5-x5m7-3935
More information
Details
Summary
The generic OpenID Connect backend (
OpenIdConnectAuthand every backend built on it) stores thenoncein the shared Association table, not in the user's session. When the ID token comes back,validate_claimsonly checks that the nonce exists in that table and is not expired. It does not check that the nonce was issued to the browser that is finishing the login.So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid
statefor their session, then hit the callback with the victim'scodeand their ownstate.statepasses because it belongs to the attacker's session, and the nonce in the victim's ID token passes because it is in the global table. The attacker's browser is now logged in as the victim.PKCE would block this, but
OpenIdConnectAuthsetsDEFAULT_USE_PKCE = False(the OAuth2 base class defaults toTrue), so the nonce is the only binding in the default setup.Tested versions
social-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1).
Details
social_core/backends/open_id_connect.pyin 6.1.1:auth_paramscallsget_and_store_nonce(self.authorization_url(), state)get_and_store_noncestores the nonce as anOpenIdConnectAssociationkeyed byserver_urlandhandle=nonce. The state goes intoassoc_typebut is never read back.get_noncelooks the nonce up byserver_urlandhandleonlyvalidate_claimsaccepts any stored, unexpired nonce and removes itDEFAULT_USE_PKCE = FalsePoC
Everything runs locally.
mockidp.pyis a small OpenID provider on 127.0.0.1 that checksredirect_uriand enforces PKCE when acode_challengewas sent, like a normal provider.social_nonce.pyuses two Django test clients as two browsers.Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails.
mockidp.py:
social_nonce.py:
Impact
An attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code.
It affects every app that uses
OpenIdConnectAuthor a backend built on it with the default settings (PKCE off).Suggested fix
Bind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to
stateinauth_params, and invalidate_claimscompare the ID token nonce with the session value before removing it. Turning PKCE on by default for the OIDC backend would also close this, and matches the OAuth2 base class.Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
CVE-2026-57178 / GHSA-3c93-f73f-qc9h / PYSEC-2026-4165
More information
Details
Impact
The
vk-appbackend accepted VK application callback data without verifying the callback signature when theauth_keyparameter 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, andapi_result, potentially allowing authentication as an arbitrary VK user ID.The issue affects only applications using the
vk-appbackend.Patches
The issue has been fixed by requiring
auth_keyto be present and valid before callback data is trusted.Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable the
vk-appbackend by removingsocial_core.backends.vk.VKAppOAuth2fromSOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to use the vulnerable backend.
Credits
Reported by @lalalala5678 through GitHub private vulnerability reporting.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
CVE-2026-57176 / GHSA-fp7w-m676-w7gc / PYSEC-2026-4166
More information
Details
Impact
The Vend OAuth2 backend used only the numeric Vend
user_idas 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.
Patches
The issue has been fixed by scoping Vend social-auth UIDs by shop.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop.
If Vend authentication is not required, the Vend backend can also be disabled by removing it from
SOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
social-auth-core has an Improper Authentication issue
CVE-2026-57175 / GHSA-vq6g-g6c7-5f2j / PYSEC-2026-4167
More information
Details
Impact
The SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued
AuthnRequest.Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker's SAML identity to a logged-in victim's local account. The attacker could then authenticate through SAML and gain access to the victim's account.
The issue affects applications using the SAML backend together with authenticated account association.
Patches
The issue has been fixed by validating SAML responses against stored
AuthnRequestIDs.Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.
If SAML login is not required, the SAML backend can also be disabled by removing it from
SOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to allow vulnerable SAML account association.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
social-auth-core has a Session Fixation issue
CVE-2026-57179 / GHSA-vqg6-3fw6-j9jg / PYSEC-2026-4168
More information
Details
Impact
The partial-pipeline resume mechanism accepted
partial_tokenas a bearer credential without binding it to the browser session that created it.Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account.
The issue affects applications using partial pipeline steps such as
mail_validationor custom steps decorated with@partial.Patches
The issue has been fixed by binding partial pipeline resumes to the originating browser session.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable resumable partial pipeline steps, including
mail_validationand custom steps decorated with@partial.If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed.
There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
CVE-2026-57177 / GHSA-x7qq-23vw-7pfg / PYSEC-2026-4169
More information
Details
Impact
The LoginRadius backend did not validate OAuth state during the authentication flow.
Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity.
The issue affects only applications using the LoginRadius backend.
Patches
The issue has been fixed by enabling callback state validation for the LoginRadius backend.
Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable the LoginRadius backend by removing it from
SOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to use the vulnerable backend.
Credits
Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.
Reporter references:
Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
CVE-2026-57178 / GHSA-3c93-f73f-qc9h / PYSEC-2026-4165
More information
Details
Impact
The
vk-appbackend accepted VK application callback data without verifying the callback signature when theauth_keyparameter 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, andapi_result, potentially allowing authentication as an arbitrary VK user ID.The issue affects only applications using the
vk-appbackend.Patches
The issue has been fixed by requiring
auth_keyto be present and valid before callback data is trusted.Users should upgrade to a patched version.
Fix:
Workarounds
Applications that cannot upgrade immediately should disable the
vk-appbackend by removingsocial_core.backends.vk.VKAppOAuth2fromSOCIAL_AUTH_AUTHENTICATION_BACKENDS.There is no complete workaround while continuing to use the vulnerable backend.
Credits
Reported by @lalalala5678 through GitHub private vulnerability reporting.
Severity
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NReferences