How severe is GHSA-vq6g-g6c7-5f2j?

GHSA-vq6g-g6c7-5f2j has a CVSS score of 6.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vq6g-g6c7-5f2j?

GHSA-vq6g-g6c7-5f2j affects the following packages: social-auth-core (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-vq6g-g6c7-5f2j?

Update social-auth-core to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vq6g-g6c7-5f2j is resolved across your whole dependency graph.

How do I detect GHSA-vq6g-g6c7-5f2j in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for social-auth-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-vq6g-g6c7-5f2j if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-vq6g-g6c7-5f2j actively exploited in the wild?

No public exploit code has been indexed for GHSA-vq6g-g6c7-5f2j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-vq6g-g6c7-5f2j?

GHSA-vq6g-g6c7-5f2j has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-vq6g-g6c7-5f2j?

GHSA-vq6g-g6c7-5f2j is classified as Improper Authentication (CWE-287). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vq6g-g6c7-5f2j published, and has it been updated?

GHSA-vq6g-g6c7-5f2j was published on September 24, 2026 and was last updated on October 1, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

social-auth-core has an Improper Authentication issueGHSA-vq6g-g6c7-5f2j

MEDIUMFix: python-social-auth/social-core#1794

GHSA-vq6g-g6c7-5f2j is a medium-severity (CVSS 6.4) Improper Authentication vulnerability in social-auth-core. A fix is available for social-auth-core — see the affected versions and patch details below.

Also known asCVE-2026-57175PYSEC-2026-4167

Published

Sep 24, 2026

Updated

Oct 1, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vq6g-g6c7-5f2j.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-vq6g-g6c7-5f2j by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐍social-auth-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

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.

Patches

The issue has been fixed by validating SAML responses against stored AuthnRequest IDs.

Users should upgrade to a patched version.

Fix:

https://github.com/python-social-auth/social-core/pull/1794

Workarounds

Applications that cannot upgrade immediately should disable SAML account association for already authenticated users.

If SAML login is not required, the SAML backend can also be disabled by removing it from SOCIAL_AUTH_AUTHENTICATION_BACKENDS.

There is no complete workaround while continuing to allow vulnerable SAML account association.

Credits

Reported through GitHub private vulnerability reporting by Liyi Zhou, Ziyue Wang, Strick, Maurice, and Chenchen Yu from the University of Sydney security research team.

Reporter references:

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`social-auth-core`	all versions	5.0.0`pip install --upgrade 'social-auth-core==5.0.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for social-auth-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update social-auth-core to 5.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vq6g-g6c7-5f2j is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

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…

Workaround published by Red Hat

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.

Source: Red Hat security advisory for GHSA-vq6g-g6c7-5f2j (CC BY 4.0)

Frequently Asked Questions

### Impact 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. ### Patches The issue has been fixed by validating S