Skip to content
Fencer Vulns
medium 6.8

CVE-2026-115910 json

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 2026-10-26 13 d ago modified 2026-10-31 9 d ago also GHSA-h2r5-x5m7-3935 , EUVD-2026-109993

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 4%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi social-auth-core 6.2.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-115910 updated cvss 6.8

social-auth-core: social-auth-core: Account takeover via improper OpenID Connect nonce binding

  • Red Hat Ansible Automation Platform 2 automation-controller 4.7.18-1.el9ap, python-social-auth-core 4.4.2-1.el9ap, python3x-social-auth-core 4.4.2-1.el8ap, ansible-automation-platform-26/hub-rhel9, ansible-automation-platform-27/hub-rhel9, python3.11-social-auth-core 4.5.4-1.el9ap, +10 more
    affected: workaround, no fix available, no fix planned “Out of support scope”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
9 d ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 4% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/python-social-auth/social-core/security/advisories/GHSA-h2r5-x5m7-3935 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi social-auth-core
<6.2.0
6.2.0

Affected products

  • python-social-auth social-core

Classification

Weakness
  • CWE-345 Insufficient Verification of Data Authenticity
  • CWE-384 Session Fixation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.