CVE-2026-67330
CVE-2026-67330 · better-auth SCIM 1.4.0-beta.27 through 1.6.21 Account Takeover via Provider-ID Collision
This page contains facts from public vulnerability sources. Check the original advisory before updating.
@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).
CVSS 9.4 · Critical · EPSS 0.6% · Fix available
- Published
- Updated
Stack: node
Affected products and versions
scim
- Versions
- ≥ 1.4.0-beta.27: Affected (semver)
No fix published
scim
- Versions
- ≥ 1.7.0-beta.0: Affected (semver)
No fix published
@better-auth/scim npm
- Affected ranges
- SEMVER: ≥ 1.4.0-beta.27, < 1.6.22
Update to 1.6.22
@better-auth/scim npm
- Affected ranges
- SEMVER: ≥ 1.7.0-beta.0, < 1.7.0-beta.10
Update to 1.7.0-beta.10