Cross-Site Request Forgery (CSRF) in social-auth-core (CVE-2026-62322)
Summary
Vulnerability in social-auth-core (CVE-2026-62322). Data can be tampered with by attackers. Mitigation: upgrade to 5.0.2 or later.
Original description
The description as published by the source.
Impact
Applications 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
Workarounds
Only applications that enable the LINE backend are affected.
Credits
Thanks to Ta Duc Thien and Duc Anh Nguyen for reproting this via GitHub.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62322 has been found in social-auth-core.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: upgrade social-auth-core to 5.0.2 or later.
If unsure, ask your IT team or search "social-auth-core CVE-2026-62322" on the vendor's site.
CVE-2026-62322 (social-auth-core) — CWE-352 / CVSS v3 6.5
Attack vector: remote (network-reachable) / unauthenticated
Patched: 5.0.2 — apply immediately
Workaround: Only applications that enable the LINE backend are affected.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in social-auth-core.
Check the vendor advisory for the affected versions of social-auth-core.
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to 5.0.2.
Workaround: Only applications that enable the LINE backend are affected.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'social-auth-core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'social-auth-core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
social-auth-coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Only applications that enable the LINE backend are affected.パッチが適用されるまでの応急処置として、Only applications that enable the LINE backend are affected. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade social-auth-core to 5.0.2ステージング環境で 5.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。