@better-auth/oauth-provider
Affected
- introduced
1.4.8-beta.7, fixed1.6.5(semver)
Fixed versions
1.6.5
Fix
- Fixed version
1.6.5npm install @better-auth/[email protected]
Advisory
Also known as: CVE-2026-41427
OAuth 2.1 Provider: Unprivileged users can register OAuth clients
Am I affected?
You're affected if all of the following are true:
If clientPrivileges is not configured, this bug has no security consequence for your deployment
---
### Summary
The clientPrivileges option documents a create action, but the OAuth client creation endpoints did not invoke the hook before persisting new clients. Deployments that configured clientPrivileges to restrict client registration were not actually restricted — any authenticated user could reach the create endpoints and register an OAuth client with attacker-chosen redirect URIs and metadata.
Non-create operations (read, list, update, delete, rotate) enforced the hook correctly. Only the create path was missing the check.
Impact
skip_consent become writable.Patches
Fixed in @better-auth/[email protected] Both create endpoints now call the clientPrivileges hook with action "create" before persisting the client record.
Workarounds
If you cannot upgrade immediately:
High Basis: The source's own band: HIGH
1.4.8-beta.7, fixed 1.6.5 (semver)1.6.5
1.6.5npm install @better-auth/[email protected]1.7.0-beta.0, last affected 1.7.0-beta.1 (semver)None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0