Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-57177 Overview
CVE-2026-57177 is a login Cross-Site Request Forgery (CSRF) vulnerability in Python Social Auth, a widely used social authentication and registration library. The flaw affects the LoginRadius backend in versions prior to 5.0.0, which failed to validate the OAuth state parameter during the authentication callback. An attacker can force a victim's browser to complete authentication using an attacker-controlled LoginRadius token, binding the victim's session to the attacker's identity. This classification maps to CWE-352: Cross-Site Request Forgery. The maintainers fixed the issue in version 5.0.0 by enabling callback state validation for the LoginRadius backend.
Critical Impact
A successful login CSRF attack authenticates the victim as the attacker's LoginRadius identity, enabling the attacker to capture data the victim subsequently enters into the account.
Affected Products
- Python Social Auth (social-core) versions prior to 5.0.0
- Applications using the LoginRadius authentication backend
- Downstream integrations such as social-auth-app-django and social-auth-app-flask that enable the LoginRadius backend
Discovery Timeline
- 2026-09-24 - CVE-2026-57177 published to NVD
- 2026-09-25 - Last updated in NVD database
Technical Details for CVE-2026-57177
Vulnerability Analysis
The vulnerability resides in the LoginRadius OAuth backend of social-core. OAuth 2.0 defines the state parameter as the primary mechanism for binding an authorization request to the originating user session. The LoginRadius backend omitted this validation on callback, so the server accepted any inbound authentication response regardless of whether it originated from a request the user initiated.
This defect enables a login CSRF attack. An attacker initiates a LoginRadius authentication flow, intercepts the callback URL containing the attacker's token, and tricks a victim into visiting that URL. The application processes the callback, exchanges the token, and establishes a session for the attacker's LoginRadius identity on the victim's browser.
User interaction is required to complete the attack, which aligns with typical phishing or malicious link delivery. The impact is limited to integrity of the authenticated session; no direct confidentiality or availability loss occurs at the authentication layer itself.
Root Cause
The LoginRadius backend did not set or verify the OAuth state nonce during the callback handler. Other backends in social-core enforce state validation by default, but LoginRadius was omitted from that control path. The fix in version 5.0.0 enables callback state validation for this backend, bringing it in line with the rest of the library.
Attack Vector
The attack is remote and requires victim interaction with an attacker-supplied link. The attacker begins a LoginRadius authentication flow against the target application and captures the resulting callback URL embedded with their own authorization code or token. The attacker then delivers the crafted callback URL to a victim through phishing, a malicious page, or an embedded redirect. When the victim's browser hits the callback endpoint, the application completes the OAuth exchange and binds the victim's session to the attacker's LoginRadius identity. See the GitHub Security Advisory GHSA-x7qq-23vw-7pfg for additional technical details.
Detection Methods for CVE-2026-57177
Indicators of Compromise
- Authentication callback requests to the LoginRadius endpoint missing a state query parameter or carrying a state value not present in any active server-side session.
- Successful account linkings where the LoginRadius identity does not match any previously used identity for the user account.
- Spikes in LoginRadius callback traffic originating from external referrers rather than the application's own login initiation URL.
Detection Strategies
- Inventory applications that import social_core.backends.loginradius and flag any instance running social-core below version 5.0.0.
- Add server-side logging that records the presence and validation outcome of the state parameter on every OAuth callback, then alert on failures or omissions.
- Correlate authentication events with user agent, IP, and session identifiers to detect sessions that switch identity ownership mid-flow.
Monitoring Recommendations
- Monitor web access logs for repeated requests to /complete/loginradius/ or equivalent callback routes without a matching initiation request.
- Alert on authentication events where the newly bound social identity differs from the user's historical identity provider usage.
- Track dependency versions in CI pipelines and raise findings when social-auth-core resolves below 5.0.0.
How to Mitigate CVE-2026-57177
Immediate Actions Required
- Upgrade social-auth-core to version 5.0.0 or later across all deployments using the LoginRadius backend.
- Audit application dependency manifests (requirements.txt, Pipfile, pyproject.toml) for pinned versions below 5.0.0 and update them.
- Invalidate active sessions and force re-authentication for users who logged in through the LoginRadius backend during the vulnerable window.
Patch Information
The fix is shipped in social-core version 5.0.0, which enables OAuth callback state validation for the LoginRadius backend. Refer to the GitHub Security Advisory GHSA-x7qq-23vw-7pfg for the vendor's authoritative remediation guidance.
Workarounds
- If an immediate upgrade is not possible, disable the LoginRadius backend by removing it from the AUTHENTICATION_BACKENDS list in the application configuration.
- Place a reverse proxy rule in front of the LoginRadius callback endpoint that rejects requests lacking a state parameter tied to a valid session cookie.
- Require users to confirm newly linked social identities through a secondary verification step before granting session access.
# Upgrade social-auth-core to the patched release
pip install --upgrade "social-auth-core>=5.0.0"
# Verify installed version
pip show social-auth-core | grep -i version
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

