CVE-2026-134311 is an authorization vulnerability in better-auth affecting versions 1.3.0 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. The flaw exists in the admin plugin's /admin/update-user endpoint, allowing users with the user:update role to modify another user's phoneNumber and phoneNumberVerified fields. This enables attackers to set a verified phone number on a higher-privileged account and potentially take over that account by signing in via phone OTP.
CVE-2026-134312 is an authentication vulnerability in better-auth versions 0.4.9 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. The flaw involves improper handling of OAuth sign-in where unverified provider emails, including those with a string "false" in the email_verified claim, are treated as verified. Additionally, mismatches in generic OAuth profile or ID-token subjects are unchecked, and Zoom provider options are ignored. This allows attackers who control an unverified email at an affected provider to sign in as the victim, link to the victim's local account, and gain session access.
Better Auth's kysely-adapter and drizzle-adapter versions before 1.7.16 and 1.8.0-beta.5 contain a race condition vulnerability involving MySQL or MariaDB serial IDs. The issue arises because the inserted row's ID is retrieved via a separate LAST_INSERT_ID() query that may execute on a different pooled connection. Under concurrent load, this can cause a user signing in to receive another user's session, allowing session hijacking.
CVE-2026-134314 affects better-auth versions 1.3.7 through before 1.7.16 and 1.8.0-beta.0 through before 1.8.0-beta.5. It involves a race condition in the emailOTP plugin's attempt counter, collision-prone email change keys, and accent-insensitive email lookups. These issues allow unauthenticated attackers to bypass the allowed OTP attempt limits via concurrent guesses, enabling brute-force attacks to sign in or reset passwords. Additionally, signed-in users can verify email addresses they do not own, and attackers with access to mail at accent-variant addresses can reset victims' passwords.
better-auth versions 1.4.0 up to but not including 1.7.16, and 1.8.0-beta.0 up to but not including 1.8.0-beta.5, contain an improper authentication vulnerability. The flaw arises because email-change links record the old and new email addresses but do not record the requesting user. This allows an attacker to reuse a valid email-change link issued for their own account after a victim registers the attacker's old email address, enabling the attacker to gain a session and change the victim's email to one they control. The issue is fixed in versions 1.7.16 and 1.8.0-beta.5.
CVE-2026-134318 is a privilege escalation vulnerability in better-auth's organization plugin affecting versions >=1.5.5 <1.7.16 and >=1.8.0-beta.0 <1.8.0-beta.5. The flaw arises because the creator role check compares the raw invitation role string without trimming, while later checks trim the string. This allows an admin or other non-creator role with invite permissions to submit a padded role string such as " owner" which is accepted as "owner" upon invitation acceptance. Exploitation can lead to unauthorized ownership privileges, enabling deletion of the organization and removal of original owners. The issue has a CVSS 4.0 score of 6.9 (medium severity) and was fixed in versions 1.7.16 and 1.8.0-beta.5.
CVE-2026-134321 is a race condition vulnerability in better-auth and @better-auth/passkey affecting versions before 1.7.16 and 1.8.0-beta.5. The flaw allows revoked sessions to remain valid due to non-atomic updates of secondary storage session lists and reliance on cookie-cached sessions. This enables attackers holding valid sessions to evade bulk revocation or bans and to use revoked cached sessions to register passkeys or create persistent sessions.
CVE-2026-134322 is an improper authentication vulnerability in better-auth affecting certain versions before 1.7.16 and 1.8.0-beta.5. The flaw exists in the phone number plugin, allowing sign-up and other flows to save unverified phone numbers. This enables attackers to associate a victim's phone number with an attacker-controlled account, causing the victim's valid OTP sign-in to yield a session for the attacker's account and potentially exposing victim data.
A concurrency issue in @better-auth/drizzle-adapter and @better-auth/kysely-adapter when using PostgreSQL for rate-limit record storage can allow bursts of concurrent requests to exceed configured rate limits. This affects versions 1.6.17 up to but not including 1.7.7 for drizzle-adapter and up to but not including 1.7.0 for kysely-adapter. The flaw weakens rate limiting on sensitive endpoints like password sign-in and two-factor verification but does not bypass authentication or directly compromise accounts.
A vulnerability in better-auth versions from 1.5.0-beta.12 up to but not including 1.7.7 with the OAuth Proxy plugin allows an attacker to sign in as another user if certain conditions are met. The issue arises when the OAuth Proxy plugin shares the same secret as the global Better Auth secret, sign-in state is stored in a cookie, and implicit account linking is enabled. An attacker who knows a user's verified email can impersonate that user without needing provider sign-in or victim interaction. The flaw is fixed in version 1.7.7.
A critical vulnerability in better-auth versions from 1.4.0-beta.18 up to but not including 1.7.7 allows an unauthenticated attacker to use the OAuth state value as a Magic Link token to sign in as any user by knowing only their email address. This bypasses email verification and OAuth provider authentication, granting full session access. The flaw affects configurations using Magic Link with default or hashed token storage combined with social or Generic OAuth sign-in and database-backed OAuth state storage. The issue is fixed in version 1.7.7.
A vulnerability in the better-auth deviceAuthorization() plugin versions from 1.3.8-beta.3 up to, but not including, 1.7.0-rc.3 allows an attacker to trick a signed-in user into approving a device login request without showing the requesting client or requested permissions. This can lead to the attacker obtaining a live session token for the user. The issue is fixed starting with version 1.7.0-rc.3.
CVE-2026-110861 is a race condition vulnerability in better-auth's drizzle-adapter and kysely-adapter affecting versions from 1.6.17 up to but not including 1.7.7 and 1.7.0 respectively. The flaw lies in the database-backed rate limiting on PostgreSQL where the check for rate limits is not atomic with the counter update. This allows remote attackers to send concurrent requests that bypass the intended rate limits on sensitive authentication endpoints such as password sign-in, two-factor verification, one-time code, and password reset.
CVE-2026-109346 is a high-severity vulnerability in better-auth versions from 1.3.8-beta.3 up to but not including 1.7.0-rc.3. It involves a user interface misrepresentation in the deviceAuthorization plugin where the GET /device endpoint omits critical information such as the client_id and scope. This omission allows attackers to initiate a device authorization request, trick signed-in users into approving it, and then redeem the authorization code to obtain a live session token. The issue is fixed in version 1.7.0-rc.3.
A vulnerability in better-auth causes stale user sessions to persist after user deletion when using external session caches and the session is not stored in the database. This affects user deletion flows in the admin, anonymous, and SCIM plugins, allowing deleted users' sessions to remain valid until the session TTL expires (default 7 days). The issue is fixed in patched versions of better-auth and @better-auth/scim, which ensure sessions are deleted before user records. Workarounds include enabling session storage in the database or explicitly revoking sessions in code. The impact is limited to session persistence post-deletion, with no known exploits in the wild.
A race condition in @better-auth/oauth-provider versions >=1.6.0 and <1.6.11 allows concurrent redemption of the same OAuth authorization code. This occurs because the token endpoint uses a non-atomic find-then-delete operation to consume single-use authorization codes, enabling multiple token sets to be issued from one code. The issue also affects legacy plugins in better-auth versions >=1.4.8-beta.7 and <1.6.0. The vulnerability violates RFC 6749's single-use code requirement and can lead to multiple valid tokens from a single authorization code.
A vulnerability in @better-auth/oauth-provider versions >=1.6.0 and <1.6.11 allows concurrent refresh token redemption to fork the refresh token family. This occurs because the refresh token rotation process is not atomic, enabling two concurrent requests using the same refresh token to both succeed and mint new tokens. This breaks the intended single-use refresh token rotation and can allow indefinite access token renewal until expiration or revocation. The issue is fixed in version 1.6.11 by implementing an atomic compare-and-swap operation during token rotation and adding a unique constraint on refresh tokens.
The better-auth library versions prior to 1.6.11, when using the legacy oidcProvider or mcp plugins, have insecure cryptographic defaults. These include advertising the 'none' algorithm for ID token signing in the discovery document, which can lead to acceptance of unsigned tokens by relying parties that do not pin algorithms. Additionally, the default acceptance of the PKCE 'plain' code challenge method violates OAuth 2.1 standards and weakens authorization code protection if the authorization URL is exposed. The newer @better-auth/oauth-provider package is not affected. A fix is available in better-auth version 1.6.11 and later.
A stored cross-site scripting (XSS) vulnerability exists in the Better Auth authorization server when using the deprecated oidc-provider or mcp plugins in versions prior to 1.6.13. The vulnerability arises from improper validation of redirect_uri values during OAuth client registration, allowing an attacker to register a javascript: URI. When the consent page navigates to this URI, attacker-controlled JavaScript executes in the authorization server origin, risking session exposure and account takeover. The issue is fixed in better-auth versions 1.6.13 and later.
A vulnerability in better-auth versions prior to 1.6.11 allows an attacker to perform account takeover via OAuth auto-linking to an unverified pre-registered email. The flaw arises because the OAuth callback implicitly links accounts based only on the OAuth provider's email verification claim, ignoring the local user's email verification status. This enables an attacker to pre-register a victim's email with an unverified password login and later have the victim's OAuth login linked to the attacker's account, granting persistent access. The issue bypasses the requireEmailVerification setting and affects all OAuth and SSO sign-in flows calling handleOAuthUserInfo. The vulnerability is fixed in better-auth 1.6.11 by requiring the local email to be verified before implicit linking.