Better Auth OAuth Provider: Refresh Token Rotation Race Condition Allows Concurrent Replay and Token Family Forking
better-auth · @better-auth oauth-provider
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @better-auth/oauth-provider npm |
|
|
| better-auth npm |
|
|
better-auth · @better-auth oauth-provider
| Product | Affected | Fixed in |
|---|---|---|
| @better-auth/oauth-provider npm |
|
|
| better-auth npm |
|
|
Better Auth is an authentication and authorization library for TypeScript. From 1.4.8-beta.7 until 1.6.11, the @better-auth/oauth-provider POST /oauth2/token endpoint on the refresh_token grant performs a non-atomic read, validate, revoke, and mint sequence on the oauthRefreshToken row, allowing concurrent requests with the same parent refresh token to pass the revoked check and create forked refresh-token families; the vulnerable range also includes embedded better-auth plugin versions before 1.6.0. This issue is fixed in version 1.6.11.
From the CVE record · GitHub_M
The @better-auth/oauth-provider POST /oauth2/token endpoint uses a non-atomic sequence when processing refresh tokens. An attacker who can submit concurrent requests with the same refresh token can pass the revoked-token check more than once and create forked refresh-token families. This also affects embedded better-auth plugin versions before 1.6.0.
Check deployments using npm @better-auth/oauth-provider >=1.6.0 <1.6.11 or better-auth >=1.4.8-beta.7 <1.6.0.