CVE-2026-67330

Critical

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

SeverityCritical
CVSS9.9
Exploit probability—
Product@better-auth/scim
PublishedAug 1, 2026
First seenAug 1, 2026

How to fix

Update
  • @better-auth/scim1.6.22, 1.7.0-beta.10 or later

Affected products

ProductAffected versionsFixed in
@better-auth/scimnpm1.4.0-beta.27 ≤ v < 1.6.22, 1.7.0-beta.0 ≤ v < 1.7.0-beta.101.6.22, 1.7.0-beta.10

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.