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

Medium 6.8 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-115910?

CVE-2026-115910 is a medium-severity vulnerability in python-social-auth social-core, published on 26 Oct 2026.

Official description

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.

Weakness: CWE-384, CWE-345

Which versions are affected by CVE-2026-115910?

2 open source packages ship an affected version, including social-auth-core.

PackageAffectedFixed in
social-auth-core PyPIAll versions6.2.0
social-auth-core PyPIAll versions6.2.0

How do I fix CVE-2026-115910?

Upgrade social-auth-core to 6.2.0 or later.

Is CVE-2026-115910 being exploited?

There is no known exploitation of CVE-2026-115910 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2026-115910, GHSA-h2r5-x5m7-3935, UBUNTU-CVE-2026-115910.

Is CVE-2026-115910 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free