{"answers":{"affected":"2 open source packages ship an affected version, including social-auth-core.","exploited":"There is no known exploitation of CVE-2026-62322 in the wild and no public exploit code.","fix":"Upgrade social-auth-core to 5.0.2 or later.","what":"CVE-2026-62322 is a medium-severity vulnerability in python-social-auth social-core, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-62322 and fix it if it is affected.\n\nWhat it is: CVE-2026-62322 is a medium-severity vulnerability in python-social-auth social-core, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-62322 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- social-auth-core (PyPI): affected all versions; fixed in 5.0.2\n- social-auth-core (PyPI): affected all versions; fixed in 5.0.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-62322/ (Markdown: https://insights.sbomify.com/CVE-2026-62322/index.md)","id":"CVE-2026-62322","markdown":"https://insights.sbomify.com/CVE-2026-62322/index.md","name":"CVE-2026-62322","record":{"aliases":["DEBIAN-CVE-2026-62322","GHSA-526j-582w-7fm9","UBUNTU-CVE-2026-62322"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Python social auth library","requires_auth":"none","summary":"Attackers can force victims into attacker-controlled accounts or link attacker identities to victim accounts via missing OAuth state validation in the LINE backend.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Python Social Auth is a social authentication/registration mechanism. Prior to 5.0.2, the LINE backend exchanges an authorization code without validating the returned OAuth state. An attacker can begin authorization for an attacker-controlled LINE account and induce a victim to visit the resulting callback URL, causing the application to log the victim into the attacker's account. When account linking is enabled, the same missing validation can link the attacker's LINE identity to the victim's existing account and create a persistent unauthorized login path. Only applications with the LINE backend enabled are affected. This issue is fixed in version 5.0.2.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Python Social Auth: Login CSRF in LINE backend (LineOAuth2) — missing OAuth state validation (incomplete fix of 5.0.0 campaign)","id":"CVE-2026-62322","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Cloudreve: Unauthorized file write via WOPI view sessions whose access token secret is ignored","id":"CVE-2026-62323"},"packages":[{"ecosystem":"PyPI","fixed":["5.0.2"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":null,"source":"GHSA-526j-582w-7fm9"},{"ecosystem":"PyPI","fixed":["5.0.2"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":"pkg:pypi/social-auth-core","source":"GHSA-526j-582w-7fm9"}],"prev":{"headline":"Logto: ReDoS via unescaped user input in email subaddressing regex (blockSubaddressing)","id":"CVE-2026-62317"},"products":["social-core"],"published":"2026-10-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-28","vendors":["python-social-auth"]},"summary":"Attackers can force victims into attacker-controlled accounts or link attacker identities to victim accounts via missing OAuth state validation in the LINE backend.","url":"https://insights.sbomify.com/CVE-2026-62322/"}