OAuth token minting via omitted client-secret verification
Published Jul 15, 2026 · Updated Jul 15, 2026
Improper authentication in Better Auth before 1.6.11 allows remote attackers to mint OAuth tokens through legacy plugin token endpoints. The oidcProvider and mcp refresh paths accept a bound refreshToken row and matching client_id without verifying a confidential client's client_secret. Exploitation requires an enabled legacy plugin, a registered confidential client, and a valid refresh token; minted tokens retain the original user's scope until revocation.
Summary
What happened
Improper authentication in Better Auth before 1.6.11 allows remote attackers to mint OAuth tokens through legacy plugin token endpoints. The oidcProvider and mcp refresh paths accept a bound refreshToken row and matching client_id without verifying a confidential client's client_secret. Exploitation requires an enabled legacy plugin, a registered confidential client, and a valid refresh token; minted tokens retain the original user's scope until revocation.
The record
- CVE
- CVE-2026-53512
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- Better Auth
- Product
- Better Auth
- Classifications
- CWE-345, CWE-287, CWE-863, CWE-306, T1528
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.6.11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo