cve.bz

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

9.4 criticalEPSS 0.6%Fix available

Critical (9.4) in better-auth scim. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in @better-auth/scim 1.6.22, 1.7.0-beta.10.

On this page
@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).

Severity

CVSS 4.0

9.4 critical
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

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 50th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-08-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @better-auth/scim (npm): fixed in 1.6.22, 1.7.0-beta.10

Ask an AI about this CVE

Show the promptExplain CVE-2026-67330 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-67330?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-67330?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-67330 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
better-auth scimfrom 1.4.0-beta.27 before 1.6.22
better-auth scimfrom 1.7.0-beta.0 before 1.7.0-beta.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-rjg6-39jm-rgg4npm@better-auth/scim>=1.4.0-beta.27 <1.6.221.6.22
GHSA-rjg6-39jm-rgg4npm@better-auth/scim>=1.7.0-beta.0 <1.7.0-beta.101.7.0-beta.10

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON