VulnerabilityPublished 11 Nov 2026

CVE-2026-126775: python-social-auth social-auth-core · Cross-Site Request Forgery (CSRF)

Affects python-social-auth social-auth-coreSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 7.0.0 when convenient.

Data as of 11 Nov 2026, 19:05 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	2.3
CNA (VulnCheck)	CVSS 3.1	4.2

Patch: Available – fixed in 7.0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: Present
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: Present: The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: a race condition must be won to successfully exploit the vulnerability (the successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker, or the attack may need to be launched multiple times against a single target before being successful); the attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade python-social-auth social-auth-core to 7.0.0.

Affected software

Product	Affected	Fixed in
python-social-authsocial-auth-core	Affected >=4.7.0 <7.0.0	Fixed in 7.0.0
PyPIsocial-auth-core`pkg:pypi/social-auth-core`Other threats	Affected >=4.7.0 <7.0.0	Fixed in 7.0.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade social-auth-core to version 7.0.0 or later, where this CSRF vulnerability in the SAML backend is fixed. No other mitigation is indicated by the vendor advisory.

Description

A Cross-Site Request Forgery (CSRF) vulnerability exists in python-social-auth's social-auth-core versions 4.7.0 through before 7.0.0 in the SAML backend. This flaw allows an attacker to craft a malicious IdP response and RelayState that, when delivered to a victim's browser, signs the victim into the attacker's account, potentially capturing data entered by the victim. The issue is fixed in version 7.0.0.

Impact

An attacker can trick a victim into logging into the attacker's account by exploiting the CSRF vulnerability in the SAML backend. This allows the attacker to capture any data the victim enters while signed into the attacker's session. The CVSS score of 2.3 and low severity rating indicate limited impact, primarily involving user session confusion rather than direct system compromise.

Summary

The social-auth-core library versions from 4.7.0 up to but not including 7.0.0 contain a CSRF vulnerability in the SAML backend. The vulnerability arises because the backend restores sessions based on the unsigned RelayState parameter, which an attacker can manipulate. By delivering a valid Identity Provider (IdP) response and RelayState via an auto-submitting form to a victim's browser, the attacker can cause the victim to be logged into the attacker's account, enabling the attacker to capture any data the victim enters during that session. This vulnerability is addressed in version 7.0.0.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 19:05 UTC

Technical details

References

Community reviews

Related threats