Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-57175 medium CVSS 6.4

Authentication Bypass in social-auth-core (CVE-2026-57175)

Summary

Authentication bypass in social-auth-core (CVE-2026-57175). Confidential information can be exposed externally. Exploitable via AuthnRequest. Mitigation: upgrade to 5.0.0 or later.

Original description

The description as published by the source.

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:

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:

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-57175 has been found in social-auth-core.
Attackers can target a specific entry point like AuthnRequest over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.4/10.
What to do: upgrade social-auth-core to 5.0.0 or later.
If unsure, ask your IT team or search "social-auth-core CVE-2026-57175" on the vendor's site.

CVE-2026-57175 (social-auth-core) — CWE-287 / CVSS v3 6.4
Attack vector: remote (network-reachable)
Attack surface: AuthnRequest / SOCIAL_AUTH_AUTHENTICATION_BACKENDS
Patched: 5.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Authentication bypass (CWE-287) exists in social-auth-core. Attackers reach the vulnerable code path via AuthnRequest.

📍 Affected scope

Check the vendor advisory for the affected versions of social-auth-core. Attack surface: AuthnRequest / SOCIAL_AUTH_AUTHENTICATION_BACKENDS.

🔥 Severity

Severity: Medium (CVSS 6.4/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 5.0.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'social-auth-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'social-auth-core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で social-auth-core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade social-auth-core to 5.0.0

    ステージング環境で 5.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip social-auth-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.0"}]}]
PyPI social-auth-core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.0.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details