CVE-2026-67330 better-auth SCIM 1.4.0-beta.27 through 1.6.21 Account Takeover via Provider-ID Collision
Authenticated users can hijack accounts by minting SCIM tokens with colliding provider IDs, allowing unauthorized access and modification of global user data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-67330?
CVE-2026-67330 is a critical authentication bypass vulnerability in better-auth scim, published on 1 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
@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).
Weakness: CWE-20
Which versions are affected by CVE-2026-67330?
4 open source packages ship an affected version, including @better-auth/scim.
| Package | Affected | Fixed in |
|---|---|---|
@better-auth/scim npm | From 1.4.0-beta.27 | 1.6.22 |
@better-auth/scim npm | From 1.4.0-beta.27 | 1.6.22 |
@better-auth/scim npm | From 1.7.0-beta.0 | 1.7.0-beta.10 |
@better-auth/scim npm | From 1.7.0-beta.0 | 1.7.0-beta.10 |
How do I fix CVE-2026-67330?
Upgrade @better-auth/scim to a fixed version for your release line: 1.6.22 or 1.7.0-beta.10.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2026-67330 being exploited?
There is no known exploitation of CVE-2026-67330 in the wild and no public exploit code.
Sources
Also known as GHSA-6mwf-73fj-3358, GHSA-rjg6-39jm-rgg4.