Login CSRF via disabled OAuth state validation
Published Sep 24, 2026 · Updated Sep 24, 2026
Login CSRF in Python Social Auth Core before 5.0.0 allows remote attackers to bind a victim session to an attacker identity. The LoginRadiusAuth backend disabled redirect-state and state-parameter handling, so its callback exchanged an attacker-supplied token without matching it to session state. Exploitation requires an application to enable LoginRadius and a victim to complete the crafted authentication flow; the victim is logged in as the attacker's LoginRadius identity.
Summary
What happened
Login CSRF in Python Social Auth Core before 5.0.0 allows remote attackers to bind a victim session to an attacker identity. The LoginRadiusAuth backend disabled redirect-state and state-parameter handling, so its callback exchanged an attacker-supplied token without matching it to session state. Exploitation requires an application to enable LoginRadius and a victim to complete the crafted authentication flow; the victim is logged in as the attacker's LoginRadius identity.
The record
- CVE
- CVE-2026-57177
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- Python Social Auth
- Product
- Python Social Auth Core
- Classifications
- CWE-352
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 5.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started