Python Social Auth is a social authentication and registration mechanism. Prior to 6.2.0, OpenIdConnectAuth in social_core/backends/open_id_connect.py uses get_and_store_nonce to place the OpenID Connect nonce in a shared OpenIdConnectAssociation table, and get_nonce and validate_claims verify only that the nonce exists and has not expired rather than binding it to the browser session and OAuth state that initiated the login. An attacker who obtains a victim's unused authorization code can start a separate login to obtain valid state for the attacker's browser, submit the victim's code with that state, and pass nonce validation because the victim nonce is globally available. With DEFAULT_USE_PKCE disabled in the default OpenIdConnectAuth configuration, the attacker can be logged in as the victim. This issue is fixed in version 6.2.0.
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 4
- StatusAwaiting Analysis → PublishedNVD modified 2026-10-26 16:44
- StatusPublished → Awaiting AnalysisNVD modified 2026-10-26 18:34
- StatusReceived → PublishedNVD modified 2026-10-26 16:44
- First seenCVSS 6.8NVD modified 2026-10-26 17:17
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.
References 4
- https://github.com/python-social-auth/social-core/commit/c2f2ae4663bef19ee8b07f2cf5a2344f9155d826
- https://github.com/python-social-auth/social-core/pull/2141
- https://github.com/python-social-auth/social-core/releases/tag/6.2.0
- https://github.com/python-social-auth/social-core/security/advisories/GHSA-h2r5-x5m7-3935