# CVE-2026-126775: Social-auth-core 4.7.0 before 7.0.0 Login CSRF via SAML RelayState

> Attackers can sign victims into an attacker's SAML account via a forged RelayState in social-auth-core's SAML backend.

- **Severity:** Low 2.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** Yes
- **Fix available:** No
- **Published:** 11 Nov 2026
- **Updated:** 11 Nov 2026
- **Also known as:** GHSA-33vc-vcr3-vj5p, GHSA-4pv2-52v7-vrfx, UBUNTU-CVE-2026-126775

## What is CVE-2026-126775?

CVE-2026-126775 is a low-severity cross-site request forgery vulnerability in python-social-auth social-auth-core, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Social-auth-core 4.7.0 before 7.0.0 contains a login cross-site request forgery vulnerability in the SAML backend that restores sessions named in the unsigned RelayState parameter. Attackers can deliver their own valid IdP response and RelayState to a victim's browser via an auto-submitting form, signing the victim into the attacker's account to capture entered data.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2026-126775?

An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.


## How do I fix CVE-2026-126775?

No fix has been published for CVE-2026-126775 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126775 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126775 and fix it if it is affected.

What it is: CVE-2026-126775 is a low-severity cross-site request forgery vulnerability in python-social-auth social-auth-core, published on 11 Nov 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-126775 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.

Affected product: python-social-auth social-auth-core. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126775/ (Markdown: https://insights.sbomify.com/CVE-2026-126775/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126775
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126775
- OSV: https://osv.dev/vulnerability/CVE-2026-126775

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126775/
Summaries are generated and may contain mistakes; the official description above is the record.
