better-auth up to 1.7.0-beta.8 @better-auth/scim authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 5.02- |
Summary
A vulnerability was found in better-auth up to 1.7.0-beta.8 and classified as critical. Affected by this issue is some unknown functionality of the component @better-auth/scim. Such manipulation leads to authorization. This vulnerability is listed as CVE-2026-67330. The attack may be performed from remote. There is no available exploit.
Details
A vulnerability was found in better-auth up to 1.7.0-beta.8. It has been rated as critical. Affected by this issue is an unknown code of the component @better-auth/scim. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Impacted is confidentiality, integrity, and availability. CVE summarizes:
@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).
The advisory is available at github.com. This vulnerability is handled as CVE-2026-67330 since 07/29/2026. The exploitation is known to be easy. The attack may be launched remotely. The technical details are unknown and an exploit is not available.
Upgrading to version 1.6.22 or 1.7.0-beta.10 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-51859). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
- 1.7.0-beta.0
- 1.7.0-beta.1
- 1.7.0-beta.2
- 1.7.0-beta.3
- 1.7.0-beta.4
- 1.7.0-beta.5
- 1.7.0-beta.6
- 1.7.0-beta.7
- 1.7.0-beta.8
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: better-auth 1.6.22/1.7.0-beta.10
Timeline
07/29/2026 CVE reserved08/01/2026 Advisory disclosed
08/01/2026 VulDB entry created
08/02/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2026-67330 (🔒)
GCVE (CVE): GCVE-0-2026-67330
GCVE (VulDB): GCVE-100-385298
EUVD: 🔒
Entry
Created: 08/01/2026 15:28Updated: 08/02/2026 01:37
Changes: 08/01/2026 15:28 (54), 08/02/2026 01:37 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.