Skip to content
Threat Brief

← All advisories

CVE-2026-67330

Critical 9.4No known exploitationFix available

better-auth SCIM 1.4.0-beta.27 before 1.6.22 Account Takeover via Provider-ID Collision

Record last updated

CVSS score

9.4

Critical on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.6%

Higher than 50% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

@better-auth/scim (a better-auth plugin) versions >= 1.4.0-beta.27 through = 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

Patching and mitigation

Patch status
Fix available (source: CVE record (VulnCheck))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
better-authscimfrom 1.4.0-beta.27 before 1.6.221.6.22CVE Program
better-authscimfrom 1.7.0-beta.0 before 1.7.0-beta.101.7.0-beta.10CVE Program

Timeline

  1. Disclosure

    CVE record published by VulnCheck

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (VulnCheck)

    Source: CVE record (VulnCheck) (opens in a new tab)

Vendor guidance and references