cve.bz

CVE-2026-57175 python-social-auth social-core: Improper Authentication

6.4 mediumEPSS 0.2%Fix available

Medium (6.4) in python-social-auth social-core. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in social-auth-core 5.0.0.

On this page
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.

Severity

CVSS 3.1

6.4 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-57175 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-57175?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-57175?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-57175 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
python-social-auth social-core< 5.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-vq6g-g6c7-5f2jPyPIsocial-auth-core<5.0.05.0.0
PYSEC-2026-4167PyPIsocial-auth-core<5.0.05.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13social-auth-coreno fix listedDEBIAN-CVE-2026-57175
Debian14social-auth-core5.0.2-1DEBIAN-CVE-2026-57175
Ubuntu22.04:LTSpython3.10no fix listedUBUNTU-CVE-2026-57175
Ubuntu24.04:LTSpython3.12no fix listedUBUNTU-CVE-2026-57175
Ubuntu26.10python3.14no fix listedUBUNTU-CVE-2026-57175
UbuntuPro:14.04:LTSpython2.7, python3.4, python3.5no fix listedUBUNTU-CVE-2026-57175
UbuntuPro:16.04:LTSpython2.7, python3.5no fix listedUBUNTU-CVE-2026-57175
UbuntuPro:18.04:LTSpython2.7, python3.6, python3.7 and 1 moreno fix listedUBUNTU-CVE-2026-57175
UbuntuPro:20.04:LTSpython2.7, python3.8, python3.9no fix listedUBUNTU-CVE-2026-57175
UbuntuPro:22.04:LTSpython2.7, python3.11no fix listedUBUNTU-CVE-2026-57175

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact for Red Hat products because exploitation requires specific non-default conditions, including an active SAML backend configured for account association alongside user interaction with an authenticated session. Additionally, an attacker must already possess valid credentials on a trusted Identity Provider to initiate the account linking process. Deployments not utilizing SAML-based identity linking or where SAML integration is disabled remain unaffected.

Red Hat's mitigation

Disable the SAML authentication backend if it is not required for your deployment. In Red Hat Ansible Automation Platform, ensure SAML authentication is disabled in Automation Controller settings (under Settings > SAML settings) and rely on alternative authentication mechanisms such as LDAP or local accounts. In custom applications utilizing python-social-auth, remove the SAML backend from `SOCIAL_AUTH_AUTHENTICATION_BACKENDS` or disable SAML account linking for authenticated sessions.

Caveats: Disabling SAML authentication prevents users from authenticating or associating accounts through SAML Identity Providers.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/controller-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/eda-controller-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/hub-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/controller-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/gateway-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/hub-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-25/lightspeed-rhel8Out of support scope
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/controller-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/gateway-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-26/lightspeed-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/gateway-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/hub-rhel9Fix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-27/lightspeed-rhel9Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ansible Automation Platform 2python3.11-social-auth-coreFix deferred
Red Hat Ansible Automation Platform 2python3.12-social-auth-coreFix deferred
Red Hat Ansible Automation Platform 2python3x-social-auth-coreOut of support scope
Red Hat Ansible Automation Platform 2python-social-auth-coreOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-57175.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON