# CVE-2026-80192: better-auth SSO before 1.6.27 Domain Ownership Authentication Bypass

> Attackers can bypass domain ownership checks in better-auth SSO to add users to their organization or link identities, requiring specific plugin configurations.

- **Severity:** High 8.6 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-8c5h-wx78-2cfg, GHSA-xfj7-7fp8-rhvp

## What is CVE-2026-80192?

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.

### Official 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-80192?


## How do I fix CVE-2026-80192?

No fix has been published for CVE-2026-80192 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-80192 being exploited?

There is no known exploitation of CVE-2026-80192 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80192 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-80192 in the wild and no public exploit code.

Affected product: better-auth sso. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80192/ (Markdown: https://insights.sbomify.com/CVE-2026-80192/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80192
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80192
- OSV: https://osv.dev/vulnerability/CVE-2026-80192

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80192/
Summaries are generated and may contain mistakes; the official description above is the record.