CVE-2026-115910: 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

Published Oct 26, 2026
·
Updated

Python Social Auth is a social authentication and registration mechanism. Prior to 6.2.0, OpenIdConnectAuth in socialcore/backends/openidconnect.py uses getandstorenonce to place the OpenID Connect nonce in a shared OpenIdConnectAssociation table, and getnonce and validateclaims 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 DEFAULTUSEPKCE disabled in the default OpenIdConnectAuth configuration, the attacker can be logged in as the victim. This issue is fixed in version 6.2.0.

Affected Software

1 affected component
pypi/social-auth-core<6.2.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Python Social Auth to a version that resolves this vulnerability.

    Fixed in 6.2.0
  2. Configuration

    Enable DEFAULT_USE_PKCE; when it is disabled, an attacker can be logged in as the victim.

    OpenIdConnectAuth DEFAULT_USE_PKCE = enabled

Event History

Oct 26, 2026
CVE Published
via MITRE·04:44 PM
Data Sourced
via MITRE·04:44 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Deployments using social-auth-core's OpenIdConnectAuth before version 6.2.0 are affected when DEFAULT_USE_PKCE is disabled, which is the default OpenIdConnectAuth configuration described here.

2

What does an attacker need to exploit this issue?

The attacker needs to obtain a victim's unused OpenID Connect authorization code. They can then initiate a separate login in their own browser to obtain valid state and submit the victim's code with that state.

3

What is the impact of a successful exploit?

A successful attacker can be logged in as the victim. The affected nonce validation accepts a globally stored, unexpired nonce without binding it to the browser session or OAuth state that initiated the victim's login.

4

What should teams do to remediate the issue?

Upgrade social-auth-core to version 6.2.0, which fixes the issue. The provided information identifies DEFAULT_USE_PKCE being disabled as a condition for exploitation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203