{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80192 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-80192 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-80192 is a high-severity authentication bypass vulnerability in better-auth sso, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80192 and fix it if it is affected.\n\nWhat it is: CVE-2026-80192 is a high-severity authentication bypass vulnerability in better-auth sso, published on 25 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80192 in the wild and no public exploit code.\n\nAffected product: better-auth sso. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-80192/ (Markdown: https://insights.sbomify.com/CVE-2026-80192/index.md)","id":"CVE-2026-80192","markdown":"https://insights.sbomify.com/CVE-2026-80192/index.md","name":"CVE-2026-80192","record":{"aliases":["GHSA-8c5h-wx78-2cfg","GHSA-xfj7-7fp8-rhvp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"better-auth SSO library","requires_auth":"low_privilege","summary":"Attackers can bypass domain ownership checks in better-auth SSO to add users to their organization or link identities, requiring specific plugin configurations.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"@better-auth/sso before 1.6.27 (and before 1.4.8 in the 1.4.x line and before 1.7.0-rc.5 in the 1.7 prerelease line) contains two domain-ownership flaws. When domain verification is disabled, automatic organization assignment accepts unverified provider domains, allowing an authenticated organization owner/administrator to register an SSO provider for an arbitrary domain and have users with matching email domains added to the attacker's organization with default member permissions. When domain verification is enabled, a race condition between the verify-domain and update-provider endpoints can apply completed DNS proof to a different domain; combined with implicit account linking, this can link an attacker-controlled identity provider to an existing user account. Exploitation requires the SSO plugin (and, for the org-assignment path, the organization plugin) with the relevant configuration enabled.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"better-auth SSO before 1.6.27 Domain Ownership Authentication Bypass","id":"CVE-2026-80192","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Kimai before 2.62.0 Authorization Bypass via QuickEntry","id":"CVE-2026-80193"},"packages":[],"prev":{"headline":"GROWI before 8.0.2 Missing Authorization on Attachment Retrieval for Unauthenticated Requests","id":"CVE-2026-80191"},"products":["sso"],"published":"2026-08-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-10-08","vendors":["better-auth"]},"summary":"Attackers can bypass domain ownership checks in better-auth SSO to add users to their organization or link identities, requiring specific plugin configurations.","url":"https://insights.sbomify.com/CVE-2026-80192/"}