CVE-2026-57175

MEDIUMPre-NVD 6.46.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.4 from GitHub Security Advisory (severity: MODERATE) published 2026-09-24. A secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-86309 (ENISA EUVD) · GHSA-vq6g-g6c7-5f2j (GitHub Security Advisories) · PYSEC-2026-4167 (OSV.dev)Source: ENISA EUVD

6.4EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.4
EG Score
6.4MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity64% × 45%
Impact severity (EG Severity): CVSS 6.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
13th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.4): severity, escalated by confirmed exploitation. This CVE's 6.4 is its impact severity (EG Severity), not escalated.

EG Severity
6.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 24, 2026

Last Modified

October 5, 2026

Advisory Details (1)

Auto-updated Sep 24, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

Improper SAML Authentication in social-auth-core · Advisory · python-social-auth/social-core · GitHub

https://github.com/python-social-auth/social-core/security/advisories/GHSA-vq6g-g6c7-5f2j

Vendor Advisories for CVE-2026-57175(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipsocial-auth-core @ 5.0.0 (fixes < 5.0.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
social-auth-core4.3.0-1 ... 5.1.1-1 (16 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
social-auth-core4.6.1-1 ... 5.1.1-1 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
social-auth-core4.6.1-1 ... 4.9.1-1 (6 versions)
  • every version up to 5.0.2-1: fixed in 5.0.2-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
social-auth-core0.0.1 ... 4.9.1 (50 versions)
  • every version up to 5.0.0: fixed in 5.0.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 48× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-11-01 07:42 UTCGHSA enrichmentGHSA-vq6g-g6c7-5f2j · GitHub severity MODERATE · GitHub CVSS 6.4
  3. 2026-11-01 07:42 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  6. 2026-10-30 10:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-25 14:17 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-22 21:07 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  21. 2026-10-18 03:29 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 40 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  3. 2026-10-12 15:54 UTCEG score recompute
  4. 2026-10-11 19:37 UTCEG score recompute
  5. 2026-10-11 16:52 UTCEG score recompute
  6. 2026-10-11 14:15 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  8. 2026-10-11 01:38 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  10. 2026-10-09 23:45 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  12. 2026-10-08 21:55 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  15. 2026-10-06 18:17 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-05 16:28 UTCEG score recompute
  19. 2026-10-05 15:48 UTCEG score recompute
  20. 2026-10-05 08:58 UTCEG score recompute
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-04 07:09 UTCEG score recompute
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  24. 2026-10-03 05:21 UTCEG score recompute
  25. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  26. 2026-10-02 03:32 UTCEG score recompute
  27. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  28. 2026-10-01 01:42 UTCEG score recompute
  29. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  30. 2026-09-29 23:54 UTCEG score recompute
  31. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  32. 2026-09-28 19:15 UTCEG score recompute
  33. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  34. 2026-09-27 17:21 UTCEG score recompute
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  37. 2026-09-26 15:28 UTCEG score recompute
  38. 2026-09-24 18:35 UTCEG score recompute
  39. 2026-09-24 17:18 UTCEG score recomputeFirst assessed: 6.4 MEDIUM
  40. 2026-09-24 17:17 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-57175?
CVE-2026-57175 is a medium-severity vulnerability; its CVE record was published on September 24, 2026. 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…
When was the CVE record for CVE-2026-57175 published?
The CVE record for CVE-2026-57175 was published on September 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 5, 2026; the record at its source may have been updated since.
Is CVE-2026-57175 actively exploited?
CVE-2026-57175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-57175?
CVE-2026-57175 has a CVSS base score of 6.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-57175?
A fix for CVE-2026-57175 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-57175 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57175

Explore →

Is Your Infrastructure Affected by CVE-2026-57175?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs