cve.bz

CVE-2026-41427 better-auth better-auth\/oauth-provider: Incorrect Authorization

7.1 highEPSS 0.2%Fix available

High (7.1) in better-auth better-auth\/oauth-provider. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @better-auth/oauth-provider 1.6.5.

On this page
Better Auth is an authentication and authorization library for TypeScript. Prior to 1.6.5, 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. This vulnerability is fixed in 1.6.5.

Severity

CVSS 4.0

7.1 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:L/SA:N

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th 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: partial, assessed 2026-04-27. 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-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41427 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41427?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41427?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-41427 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

  • better-auth:better-auth\/oauth-provider

Versions

From the NVD's CPE matches.

ProductAffected
better-auth:better-auth/oauth-providerfrom 1.4.9 before 1.6.5
better-auth:better-auth/oauth-provider1.4.8
better-auth:better-auth/oauth-provider1.4.8:beta7
better-auth:better-auth/oauth-provider1.7.0:beta0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xr8f-h2gw-9xh6npm@better-auth/oauth-provider>=1.4.8-beta.7 <1.6.51.6.5
GHSA-xr8f-h2gw-9xh6npm@better-auth/oauth-provider>=1.7.0-beta.0 <=1.7.0-beta.1no fix published

References

Check your stackJSON