NVD / CVE Program· CNA GitHub_M

CVE-2026-57175: social-auth-core has an Improper Authentication issue

Noroxi assessment

Priority: Monitor (action score 25/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. Special conditions such as timing or configuration are required.
Fixed version: python-social-auth social-core 5.0.0.

Low priority for now. Upgrade to python-social-auth social-core 5.0.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 6.4 · v3.1—No exploit Fix available

Auth bypass

Published: Sep 24, 2026
Updated: Oct 5, 2026
EPSS: 0.2% · 13th percentile
CWE: CWE-287

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 25 / 40 · 6.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 6.4; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

python-social-auth social-core
- < 5.0.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	social-auth-core	from 0	—
Debian:14	social-auth-core	before 5.0.2-1	5.0.2-1
PyPI	social-auth-core	before 5.0.0	5.0.0

Same product

python-social-auth: all records

Other highest-scoring records for the same primary product.

CVE-2026-57178social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
29Monitor
CVE-2026-115910Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
27Monitor
CVE-2026-57176social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
27Monitor

Published before and after this one in the same product

Later →CVE-2026-57177Sep 24, 2026 · social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
17Monitor
Later →CVE-2026-57179Sep 24, 2026 · social-auth-core has a Session Fixation issue
16Monitor
Later →CVE-2026-62322Oct 15, 2026 · Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
26Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
python-social-auth social-core	5.0.0 · description	Vendor (CNA)
debian:social-auth-core	5.0.2-1 · Debian:14	Package registry (OSV)
PyPI:social-auth-core	5.0.0	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-571780 days apartsocial-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
29Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
A user must open a link or visit a page.
Special conditions such as timing or configuration are required.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: none

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1app.use("/admin", requireSession, adminRouter);
2

3// Route added later skips the middleware
4app.post("/admin-api/config", updateConfig);

Fixed

1const admin = express.Router();
2admin.use(requireSession, requireRole("admin"));
3

4admin.post("/config", updateConfig);
5app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

SSVC exploitation— → noneOct 5, 2026, 5:07 PM UTC
Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

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

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records