CVE-2026-57177

social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend

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:

• https://lzhou1110.github.io/
• https://zyy0530.github.io/
• https://str1ckl4nd.github.io/
• https://maurice.busystar.org/
• https://7thparkk.github.io/

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.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2026-57177 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.0.0); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The issue has been fixed by enabling callback state validation for the LoginRadius backend.

Users should upgrade to a patched version.

Fix:

• https://github.com/python-social-auth/social-core/pull/1808

1. What is CVE-2026-57177? CVE-2026-57177 is a medium-severity cross-site request forgery (CSRF) vulnerability in social-auth-core (pip), affecting versions < 5.0.0. It is fixed in 5.0.0. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2026-57177? CVE-2026-57177 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of social-auth-core are affected by CVE-2026-57177? social-auth-core (pip) versions < 5.0.0 is affected.
4. Is there a fix for CVE-2026-57177? Yes. CVE-2026-57177 is fixed in 5.0.0. Upgrade to this version or later.
5. Is CVE-2026-57177 exploitable, and should I be worried? Whether CVE-2026-57177 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-57177 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-57177? Upgrade social-auth-core to 5.0.0 or later.

Other vulnerabilities in social-auth-core