social-auth-core
Python Social Auth - Core
Activity
- Latest release
- 1w ago
- Total releases
- 60
- Cadence
- ~36 days
- Last 12 months
- 18
Reach
- Stars
- 922
Details
- License
- BSD-3-Clause
- First release
- Nov 27, 2016
| Version | Released | |
|---|---|---|
6.2.0
minor
| ||
6.1.1
patch
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
6.1.0
minor
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
6.0.0
major
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
5.2.0
minor
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
5.1.1
patch
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
5.1.0
minor
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
5.0.2
patch
1 CVE
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev | ||
5.0.1
patch
2 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev | ||
5.0.0
major
2 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev | ||
4.9.1
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.9.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.7
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.6
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.5
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.4
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.3
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.2
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.1
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.8.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.7.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.6.1
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.6.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.6
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.5
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.4
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.3
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.2
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.1
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.5.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.4.2
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.4.1
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.4.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.3.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.2.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.1.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.0.3
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.4.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
4.0.2
major
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.3.3
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.3.2
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.3.1
patch
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.3.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.2.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.1.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
3.0.0
major
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
2.0.0
major
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
1.7.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
1.6.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev | ||
1.5.0
minor
7 CVEs
CVE-2026-115910
GHSA-h2r5-x5m7-3935
Oct 28, 2026
Python Social Auth: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim
6.8
/ 10
Medium
Network
High
None
Required
Unchanged
High
High
None
SummaryThe generic OpenID Connect backend ( So the nonce does not do its job. OIDC Core (section 15.5.2) and RFC 9700 (section 4.5) use the nonce to stop authorization code injection: an attacker who gets hold of a victim's unused authorization code should not be able to redeem it in the attacker's own browser. With social-auth-core, the attacker can. They start their own login to get a valid PKCE would block this, but Tested versionssocial-auth-core 6.1.1 (latest), 6.1.0 and 5.2.0, with social-auth-app-django 7.1.0 and Django 6.1.2, Python 3.14. The same code is on master (098ef399c1). Details
PoCEverything runs locally.
Output on 6.1.1:
Controls:
So the nonce check runs, but it accepts a nonce that belongs to another browser. With PKCE on, the same attack fails. mockidp.py:
social_nonce.py:
ImpactAn attacker who gets a victim's authorization code before it is used can log in to the relying party as the victim. Codes leak in practice through the callback URL: Referer headers, proxy or server logs, browser history and sync, a malicious browser extension, or an open redirect on the callback. This is the exact case the OIDC nonce is meant to cover. The attacker does not need the client secret, because the relying party itself redeems the code. It affects every app that uses Suggested fixBind the nonce to the session that started the login. For example, keep the nonce (or a hash of it) in the session next to Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 47 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
5.0.2
5.1.0
5.1.1
5.2.0
6.0.0
6.1.0
6.1.1
Fixed in
6.2.0
References
Updated Oct 28, 2026 · Source: OSV.dev
CVE-2026-62322
GHSA-526j-582w-7fm9
Oct 15, 2026
Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)
6.5
/ 10
Medium
Network
Low
None
Required
Unchanged
None
High
None
ImpactApplications using the LINE Login backend are vulnerable to login CSRF / forced authentication. An attacker can start a LINE authorization flow for an account they control and trick a victim into visiting the callback URL with the attacker’s authorization code. Because the LINE backend did not validate the returned OAuth state, the application could accept the forged callback and log the victim in as the attacker-controlled LINE account. If account linking is enabled, the same flaw can allow an attacker to link their LINE identity to a victim’s existing authenticated account, creating a persistent unauthorized login path. Patches
WorkaroundsOnly applications that enable the LINE backend are affected. CreditsThanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 40 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
5.0.0
5.0.1
Fixed in
5.0.2
References
Updated Oct 15, 2026 · Source: OSV.dev
CVE-2026-57179
PYSEC-2026-4168
GHSA-vqg6-3fw6-j9jg
Oct 01, 2026
social-auth-core has a Session Fixation issue
4.2
/ 10
Medium
Network
High
None
Required
Unchanged
Low
Low
None
ImpactThe partial-pipeline resume mechanism accepted Applications using resumable partial pipeline steps could allow an attacker to start an authentication flow, obtain a valid partial token and verification data, and cause a victim's browser to resume that attacker-controlled flow. This could authenticate the victim's browser as the attacker's account. The issue affects applications using partial pipeline steps such as PatchesThe issue has been fixed by binding partial pipeline resumes to the originating browser session. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable resumable partial pipeline steps, including If those flows are required, applications should avoid accepting partial resume links from untrusted contexts until a patched version can be deployed. There is no complete workaround while continuing to use the vulnerable partial-pipeline resume mechanism. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57178
PYSEC-2026-4165
GHSA-3c93-f73f-qc9h
Oct 01, 2026
social-auth-core: VK App backend accepts unsigned callback data when auth_key is missing
7.4
/ 10
High
Network
High
None
None
Unchanged
High
High
None
ImpactThe Applications using this backend could treat unsigned attacker-controlled data as a verified VK identity. An attacker could choose callback fields such as The issue affects only applications using the PatchesThe issue has been fixed by requiring Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the There is no complete workaround while continuing to use the vulnerable backend. CreditsReported by @lalalala5678 through GitHub private vulnerability reporting. Affected versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57177
PYSEC-2026-4169
GHSA-x7qq-23vw-7pfg
Oct 01, 2026
social-auth-core has Login CSRF via Missing State Parameter in LoginRadius Backend
4.3
/ 10
Medium
Network
Low
None
Required
Unchanged
None
Low
None
ImpactThe LoginRadius backend did not validate OAuth state during the authentication flow. Applications using this backend were vulnerable to login CSRF. An attacker could cause a victim's browser session to complete authentication using an attacker-controlled LoginRadius token, making the victim authenticated as the attacker's LoginRadius identity. The issue affects only applications using the LoginRadius backend. PatchesThe issue has been fixed by enabling callback state validation for the LoginRadius backend. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should disable the LoginRadius backend by removing it from There is no complete workaround while continuing to use the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57176
PYSEC-2026-4166
GHSA-fp7w-m676-w7gc
Oct 01, 2026
social-auth-core Vulnerable to Account Takeover via Identity Binding Flaw in Vend Backend
6.8
/ 10
Medium
Network
High
Low
None
Unchanged
High
High
None
ImpactThe Vend OAuth2 backend used only the numeric Vend When multiple Vend shops authenticate through the same application, users from different shops with the same internal Vend user ID could collide in the social-auth association table. A user from one shop could then be authenticated as the local account previously associated with the same numeric user ID from another shop. The issue affects applications using the Vend OAuth2 backend with more than one Vend shop. PatchesThe issue has been fixed by scoping Vend social-auth UIDs by shop. Users should upgrade to a patched version. Fix:
WorkaroundsApplications that cannot upgrade immediately should restrict the Vend OAuth2 backend to a single trusted Vend shop. If Vend authentication is not required, the Vend backend can also be disabled by removing it from There is no complete workaround while continuing to allow authentication from multiple Vend shops with the vulnerable backend. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev
CVE-2026-57175
PYSEC-2026-4167
GHSA-vq6g-g6c7-5f2j
Oct 01, 2026
social-auth-core has an Improper Authentication issue
6.4
/ 10
Medium
Network
High
Low
Required
Unchanged
High
High
None
ImpactThe SAML backend accepted SAML responses on the Assertion Consumer Service endpoint without verifying that they matched a previously issued 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. PatchesThe issue has been fixed by validating SAML responses against stored Users should upgrade to a patched version. Fix:
WorkaroundsApplications 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 There is no complete workaround while continuing to allow vulnerable SAML account association. CreditsReported 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 versions
0.0.1
0.1.0
0.2.0
0.2.1
1.0.0
1.0.1
1.1.0
1.2.0
1.3.0
1.4.0
1.5.0
1.6.0
+ 38 more Show less
1.7.0
2.0.0
3.0.0
3.1.0
3.2.0
3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
4.0.2
4.0.3
4.1.0
4.2.0
4.3.0
4.4.0
4.4.1
4.4.2
4.5.0
4.5.1
4.5.2
4.5.3
4.5.4
4.5.5
4.5.6
4.6.0
4.6.1
4.7.0
4.8.0
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
4.8.7
4.9.0
4.9.1
Fixed in
5.0.0
References
Updated Oct 01, 2026 · Source: OSV.dev |