Vulnerability 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).
CVSS Score
CRITICAL
Related Weaknesses (CWE)
References
- https://github.com/better-auth/better-auth/security/advisories/GHSA-rjg6-39jm-rg
- https://www.vulncheck.com/advisories/better-auth-scim-beta-27-through-account-ta
FAQ
What is CVE-2026-67330?
CVE-2026-67330 is a vulnerability with a CVSS score of 9.9 (CRITICAL). @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 pro...
How severe is CVE-2026-67330?
CVE-2026-67330 has been rated CRITICAL with a CVSS base score of 9.9/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2026-67330?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.