Vulnerability in @better-auth/scim (CVE-2026-67330)
Summary
Vulnerability in @better-auth/scim (CVE-2026-67330). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.6.22 or later.
Original description
The description as published by the source.
@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).
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-67330 has been found in @better-auth/scim.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade @better-auth/scim to 1.6.22 or later.
If unsure, ask your IT team or search "@better-auth/scim CVE-2026-67330" on the vendor's site.
CVE-2026-67330 (@better-auth/scim) — CWE-20 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.6.22 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in @better-auth/scim.
Check the vendor advisory for the affected versions of @better-auth/scim.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 1.6.22.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@better-auth/scim' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@better-auth/scim' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@better-auth/scimを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @better-auth/scim to 1.6.22ステージング環境で 1.6.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com