Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-h2r5-x5m7-3935

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

CVSS 6.8 MediumEPSS 0.0016 · 4th percentile

Published by the GitHub Advisory Database at 28 Oct 2026, 21:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
social-auth-corePyPI<6.2.06.2.0
Identifiers
GHSA-h2r5-x5m7-3935 · CVE-2026-115910
Weakness (CWE)
CWE-345 · CWE-384
Tags
Published
28 Oct 2026
Updated
28 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Affected versions of social-auth-core before 6.2.0 have an OpenID Connect nonce that is stored in a shared table rather than bound to the browser session, so the ID token nonce check does not confirm the login was started by the same browser. An attacker who obtains a victim's unused authorization code (for example from a leaked callback URL) could redeem it in their own browser and be logged in as the victim, with default settings where PKCE is off. Upgrade social-auth-core to 6.2.0 or later.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.8 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 4th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 26 Oct 2026, 16:44 UTC Confirmed by the CVE List
  2. 31 Oct 2026, 14:07 UTC First seen by agentprime
  3. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.