CVE-2026-67330

published 1 Aug 2026 · updated 20 Nov 2026

better-auth SCIM 1.4.0-beta.27 before 1.6.22 Account Takeover via Provider-ID Collision

9.9CriticalCVSS 9.9EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.6.22 and 1.7.0-beta.10.

@better-auth/scim (a better-auth plugin) versions >= 1.4.0-beta.27 through <= 1.6.21 and >= 1.7.0-beta.0 through <= 1.7.0-beta.9 contain an authorization bypass. SCIM token issuance did not reject provider IDs already used by existing SSO, SAML, OIDC, generic OAuth, or social account providers, and the same logical provider ID was used for both SCIM provider configuration and account ownership. An authenticated user could mint a SCIM token whose provider ID collided with an existing provider namespace, causing SCIM user routes to resolve account rows the token never provisioned. This allowed listing, reading, updating (including rewriting global profile/email fields without uniqueness checks), and deleting global user accounts and sessions, resulting in account takeover and unauthorized deprovisioning. Fixed in 1.6.22 and 1.7.0-beta.10 (1.7.0-rc.0).

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
better-auth>=1.4.0-beta.27 <1.6.22, >=1.7.0-beta.0 <1.7.0-beta.101.6.22, 1.7.0-beta.10

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-67330 severity on Zeptric[![CVE-2026-67330](https://zeptric.io/badge/cve/CVE-2026-67330.svg)](https://zeptric.io/cve/CVE-2026-67330)