{"answers":{"affected":"2 open source packages ship an affected version, including social-auth-core.","exploited":"There is no known exploitation of CVE-2026-115910 in the wild and no public exploit code.","fix":"Upgrade social-auth-core to 6.2.0 or later.","what":"CVE-2026-115910 is a medium-severity vulnerability in python-social-auth social-core, published on 26 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-115910 and fix it if it is affected.\n\nWhat it is: CVE-2026-115910 is a medium-severity vulnerability in python-social-auth social-core, published on 26 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-115910 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- social-auth-core (PyPI): affected all versions; fixed in 6.2.0\n- social-auth-core (PyPI): affected all versions; fixed in 6.2.0\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-115910/ (Markdown: https://insights.sbomify.com/CVE-2026-115910/index.md)","id":"CVE-2026-115910","markdown":"https://insights.sbomify.com/CVE-2026-115910/index.md","name":"CVE-2026-115910","record":{"aliases":["DEBIAN-CVE-2026-115910","GHSA-h2r5-x5m7-3935","UBUNTU-CVE-2026-115910"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Python Social Auth is a social authentication and registration mechanism. Prior to 6.2.0, OpenIdConnectAuth in social_core/backends/open_id_connect.py uses get_and_store_nonce to place the OpenID Connect nonce in a shared OpenIdConnectAssociation table, and get_nonce and validate_claims verify only that the nonce exists and has not expired rather than binding it to the browser session and OAuth state that initiated the login. An attacker who obtains a victim's unused authorization code can start a separate login to obtain valid state for the attacker's browser, submit the victim's code with that state, and pass nonce validation because the victim nonce is globally available. With DEFAULT_USE_PKCE disabled in the default OpenIdConnectAuth configuration, the attacker can be logged in as the victim. This issue is fixed in version 6.2.0.","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: OpenID Connect nonce is not bound to the browser session, so a stolen authorization code logs the attacker in as the victim","id":"CVE-2026-115910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"vLLM: DoS via unbounded chat_template Jinja2 rendering exhausts the renderer thread pool","id":"CVE-2026-115911"},"packages":[{"ecosystem":"PyPI","fixed":["6.2.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":null,"source":"GHSA-h2r5-x5m7-3935"},{"ecosystem":"PyPI","fixed":["6.2.0"],"introduced":["0"],"last_affected":[],"package":"social-auth-core","purl":"pkg:pypi/social-auth-core","source":"GHSA-h2r5-x5m7-3935"}],"prev":{"headline":"zip: Unbounded Symlink-Target Handling Can Abort Or Exhaust Memory During Extraction","id":"CVE-2026-115909"},"products":["social-core"],"published":"2026-10-26","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-26","vendors":["python-social-auth"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-115910/"}