# CVE-2026-57175: social-auth-core has an Improper Authentication issue > Attackers can link their SAML identity to a victim's account via improper authentication checks, leading to account takeover in applications using SAML account association. - **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 24 Sep 2026 - **Updated:** 5 Oct 2026 - **Also known as:** DEBIAN-CVE-2026-57175, GHSA-vq6g-g6c7-5f2j, PYSEC-2026-4167, UBUNTU-CVE-2026-57175 ## What is CVE-2026-57175? CVE-2026-57175 is a medium-severity authentication bypass vulnerability in python-social-auth social-core, published on 24 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description Python Social Auth is a social authentication/registration mechanism. Prior to version 5.0.0, the SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued `AuthnRequest`. Applications using SAML account association could allow an attacker with a valid account on a trusted IdP to link the attacker's SAML identity to a logged-in victim's local account. The attacker could then authenticate through SAML and gain access to the victim's account. The issue affects applications using the SAML backend together with authenticated account association. The issue has been fixed in version 5.0.0 by validating SAML responses against stored `AuthnRequest` IDs. Weakness: CWE-287 (Improper Authentication) ## Which versions are affected by CVE-2026-57175? 3 open source packages ship an affected version, including social-auth-core. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `social-auth-core` | PyPI | All versions | 5.0.0 | | `social-auth-core` | PyPI | All versions | 5.0.0 | | `social-auth-core` | PyPI | All versions | 5.0.0 | ## How do I fix CVE-2026-57175? Upgrade social-auth-core to 5.0.0 or later. ## Is CVE-2026-57175 being exploited? There is no known exploitation of CVE-2026-57175 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-57175 and fix it if it is affected. What it is: CVE-2026-57175 is a medium-severity authentication bypass vulnerability in python-social-auth social-core, published on 24 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-57175 in the wild and no public exploit code. Affected packages and fixed versions: - social-auth-core (PyPI): affected all versions; fixed in 5.0.0 - social-auth-core (PyPI): affected all versions; fixed in 5.0.0 - social-auth-core (PyPI): affected all versions; fixed in 5.0.0 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-57175/ (Markdown: https://insights.sbomify.com/CVE-2026-57175/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-57175 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-57175 - OSV: https://osv.dev/vulnerability/CVE-2026-57175 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-57175/ Summaries are generated and may contain mistakes; the official description above is the record.