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: - Using @better-auth/oauth-provider at version specified below - You configured clientPrivileges in the plugin options expecting it to gate who can create OAuth clients - The /oauth2/create-client or /admin/oauth2/create-client endpoints are reachable by authenticated users you don't fully trust If clientPrivileges is not configured, this bug has no…
Published Apr 16, 2026 · Updated Apr 27, 2026
Affected packages
@better-auth/oauth-provider
- Ecosystem
- npm
- Affected
- >= 1.4.8-beta.7, < 1.6.5
- Fixed in
- 1.6.5
- Check
npm ls @better-auth/oauth-provider
@better-auth/oauth-provider
- Ecosystem
- npm
- Affected
- >= 1.7.0-beta.0, <= 1.7.0-beta.1
- Fixed in
- No patched version yet
- Check
npm ls @better-auth/oauth-provider
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Am I affected?
You're affected if all of the following are true:
- Using @better-auth/oauth-provider at version specified below
- You configured clientPrivileges in the plugin options expecting it to gate who can create OAuth clients
- The /oauth2/create-client or /admin/oauth2/create-client endpoints are reachable by authenticated users you don't fully trust
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
- Unauthorized registration of OAuth clients by any authenticated user, under deployments that expected clientPrivileges to block them.
- Attacker-controlled redirect_uris on those clients enable phishing flows that present as registered first-party applications.
- If the SERVER_ONLY admin creation endpoint is also exposed to low-privilege users (a separate deployment misconfiguration), additional sensitive fields including
skip_consentbecome 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:
- Block the /oauth2/create-client and /admin/oauth2/create-client routes at your reverse proxy or middleware layer for any user who should not be able to register clients.
- Do not expose the admin creation endpoint (it is SERVER_ONLY by design and should not be reachable by end-user sessions).
Credited to chdanielmueller.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-53517
Better Auth: OAuth refresh-token rotation forks the token family on concurrent redemption
high8.1Jul 7, 2026CVE-2026-53518
@better-auth/oauth-provider's OAuth authorization-code grant allows concurrent redemption when two token requests race the find-then-delete primitive
high8.1Jul 7, 2026GHSA-p2fr-6hmx-4528
@better-auth/oauth-provider may provide access tokens for unauthorized audiences via unbound resource indicators
medium6.4Jul 7, 2026
