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

Published Aug 25, 2026
·
Updated

@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.

Affected Software

3 affected components
npm/@better-auth/sso<1.6.27
npm/@better-auth/sso>1.4.0<=1.4.8
npm/@better-auth/sso<1.7.0-rc.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade @better-auth/sso to a version that resolves this vulnerability.

    Fixed in 1.6.27Patch better-auth SSO before 1.6.27 Domain Ownership Authentication Bypass
  2. Upgrade

    Upgrade @better-auth/sso to a version that resolves this vulnerability.

    Fixed in 1.4.8Patch better-auth SSO before 1.6.27 Domain Ownership Authentication Bypass
  3. Upgrade

    Upgrade @better-auth/sso to a version that resolves this vulnerability.

    Fixed in 1.7.0-rc.5Patch better-auth SSO before 1.6.27 Domain Ownership Authentication Bypass
  4. Compensating control

    Ensure the Better Auth SSO plugin (and, for the org-assignment path, the organization plugin) is not enabled unless required, since exploitation requires these plugins with the relevant configuration enabled.

Event History

Aug 25, 2026
CVE Published
via MITRE·11:19 PM
Data Sourced
via MITRE·11:19 PM
DescriptionSeverityWeakness
Aug 26, 2026
Data Sourced
via NVD·05:18 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

Affected deployments use the @better-auth/sso plugin. The automatic organization-assignment path additionally requires the organization plugin and its relevant configuration to be enabled.

2

What access does an attacker need for the automatic organization-assignment path?

The attacker must be an authenticated organization owner or administrator. They can then register an SSO provider for an arbitrary domain when domain verification is disabled.

3

Which versions contain fixes?

Upgrade to 1.6.27 or later. For the 1.4.x line, upgrade to 1.4.8 or later; for the 1.7 prerelease line, upgrade to 1.7.0-rc.5 or later.

4

How can I assess whether my configuration is exposed?

Check whether the SSO plugin is installed and whether automatic organization assignment is enabled with domain verification disabled. Also review deployments with domain verification enabled that use the verify-domain and update-provider endpoints together with implicit account linking.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203