CVE-2026-67330 json
better-auth SCIM 1.4.0-beta.27 through 1.6.21 Account Takeover via Provider-ID Collision
published 2026-07-24 3 mo ago modified 2026-10-23 16 d ago also GHSA-rjg6-39jm-rgg4 , EUVD-2026-51859
- cvss
- 9.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
@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).
Patch / fix
- npm @better-auth/scim 1.6.22, 1.7.0-beta.10
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 3 mo ago
Exploit prediction
0.60% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.4 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H |
| CNA | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| CNA | 4.0 | 9.4 | CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.1 | 9.9 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @better-auth/scim | >=1.4.0-beta.27, <1.6.22 >=1.7.0-beta.0, <1.7.0-beta.10 |
1.6.22 1.7.0-beta.10 |
Affected products
- better-auth scim
Classification
References
-
github.com
/better-auth/better-auth/pull/10242
web
-
github.com
/better-auth/better-auth/commit/7c126dcd1aad24468ec37e876545c1d083d8acca
web
-
github.com
/better-auth/better-auth/security/advisories/GHSA-rjg6-39jm-rgg4
vendor-advisory, web
-
vulncheck.com
/advisories/better-auth-scim-beta-27-through-account-takeover-via-provider-id-collision
third-party-advisory
-
github.com
/better-auth/better-auth
package
-
github.com
/better-auth/better-auth/releases/tag/v1.6.22
web
-
github.com
/better-auth/better-auth/releases/tag/v1.7.0-beta.10
web
Sources
- CVE List CVE-2026-67330
- GitHub Advisory GHSA-rjg6-39jm-rgg4
- NVD CVE-2026-67330
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.