Better Auth release notes, breaking changes, and upgrade notes.
The most comprehensive authentication framework for TypeScript StackPulse turns upstream changelogs into scannable summaries with risky changes, deprecations, migration notes, and source links.
This release adds an explicit DPoP-binding enforcement step for endpoints that accept DPoP-bound tokens and clarifies that `requireActiveAccessToken` does not enforce that binding. It also improves verification cleanup efficiency and fixes OAuth/provider and package interoperability issues, including errors caused by multiple copies of `better-call`.
affected
Applications that accept DPoP-bound tokens need to add explicit endpoint-level binding enforcement; users of the affected packages also benefit from fixes to verification cleanup, error handling, dependency sharing, and OAuth discovery URLs.
action
If your endpoints accept DPoP-bound tokens, add the documented `enforceDpopBinding` call with a shared replay store.
release_signals
!Applications accepting DPoP-bound tokens must enforce DPoP binding with `enforceDpopBinding`; `requireActiveAccessToken` checks token activity only and does not enforce DPoP binding.
+Introduces `enforceDpopBinding` from `better-auth/oauth2` for enforcing DPoP binding at endpoints that accept DPoP-bound tokens.
migration_steps1 steps
01If you accept DPoP-bound tokens, call `enforceDpopBinding` from `better-auth/oauth2` in the endpoint, passing the request and a shared replay store.
This prerelease adds server-provided DPoP nonce support and makes OAuth client-secret expiration persist and be enforced. It introduces single-use server-issued nonces for client-submitted ID tokens and Google One Tap, and tightens OAuth Authorization-header handling; these changes include breaking behavior and required database migration steps for some adapters.
affected
Applications using generic OAuth Authorization headers, client-submitted provider ID tokens, Google One Tap callbacks, OAuth provider client secrets, or affected database adapters may need configuration or schema updates.
action
Review the OAuth and One Tap breaking changes and apply the documented adapter migration before deploying; enable `requireIssuedIdTokenNonce` only if the application is prepared to issue and submit nonces.
This release fixes issues across OAuth, SSO, database adapters, SCIM, and Cloudflare Workers, including token refresh behavior, SAML replay protection, and intermittent startup failures. It also changes Prisma `update` to affect only one matching row and requires native adapter transactions for SCIM provisioning; MongoDB index build failures now require correcting the underlying cause before restarting.
affected
Applications using SCIM with adapters lacking native transactions, MongoDB index creation, or Prisma updates on non-unique filters are directly affected; OAuth, SSO, and Cloudflare Workers users also receive relevant fixes.
action
Review the listed SCIM, MongoDB index, and Prisma update action items before upgrading.
release_signals
-Prisma adapter `update` now changes only one matching row; use `updateMany` when all rows matching a non-unique filter must be changed.
v1.7.20mediumsecurityNov 10, 2026
v1.7.20
This release fixes OAuth public-client prelogin validation, token endpoint defaults, and support for HTTP deployments on private networks. It also corrects database adapter filtering behavior and applies the default SAML clock skew when validating assertion time bounds.
affected
Users of the OAuth provider, Prisma or memory adapters, and SSO/SAML validation may benefit from these behavior fixes.
release_signals
!OAuth public-client prelogin now returns a client only when its client_id matches the signed oauth_query; mismatches receive 401 invalid_client.
This release fixes authentication and authorization issues across Better Auth and its provider, passkey, Expo, Electron, and Stripe packages. Key fixes prevent revoked or unverified sessions and identities from being accepted, bind verification and authorization flows to the correct account or browser session, and tighten origin and role checks. It also changes the permission required for admin phone-number updates and how server code sets Stripe customer IDs.
affected
Applications using Better Auth’s admin phone updates, Stripe integration, session caching, OAuth, passkeys, or desktop and mobile authorization flows may be affected by these fixes and behavior changes.
action
Review custom access-control statements and any server-side Stripe customer ID updates, then upgrade to v1.7.16.
release_signals
-Admin phone-number updates now require the `user:set-phone` permission; custom access-control statements must include `set-phone` to allow this operation.
v1.7.15highsecurityNov 1, 2026
v1.7.15
This release fixes bugs across Better Auth, its CLI, and several plugins, including metadata handling, session enforcement, OAuth flows, and secondary API-key storage. It also tightens Stripe callback URL validation and prevents built-in social-provider requests from following HTTP redirects.
affected
Better Auth users and operators of its CLI, Stripe, API-key, CIMD, and core OAuth integrations may benefit from these bug and security-related fixes.
action
Upgrade to v1.7.15 to receive the listed fixes, particularly the Stripe redirect validation and social-provider redirect changes.
release_signals
!Stripe subscription success now validates the resolved callback URL against trusted origins, preventing redirects to untrusted origins through checkoutSessionId.
!Built-in social providers no longer follow HTTP redirects for token exchange, refresh, verification, or JWKS signing-key requests.
-
Generic OAuth now fails at startup if `authorizationHeaders` includes `Authorization`; token request functions throw if `headers` includes `authorization`. Configure credentials through `customizeRequest` with `tokenEndpointAuth` method `custom`, setting all credentials required by the provider.
-ID-token sign-in and account linking can require server-issued single-use nonces when `requireIssuedIdTokenNonce` is enabled; requests without an issued nonce or with a reused nonce are rejected. Built-in verification rejects opaque tokens when a nonce is also supplied.
-`/one-tap/callback` now requires a single-use nonce obtained from `POST /one-tap/nonce`; client-provided nonce configuration must be removed.
!Single-use server-issued nonces bind client-submitted ID tokens to a request and prevent token reuse when the option is enabled; Google One Tap callbacks also require a single-use nonce.
!OAuth provider client-secret expiry is now saved, returned as `client_secret_expires_at`, and enforced with `invalid_client` at token, introspection, and revocation endpoints.
+Added server-provided DPoP nonce support for OAuth providers and resource servers, including `dpop: { nonce: { required: true } }`, `verifyAccessTokenRequest`, `createResourceServerChallenge`, and `createDpopNonce`.
+Added optional server-issued, single-use nonce binding for client-submitted provider ID tokens via `requireIssuedIdTokenNonce`.
+Added `POST /one-tap/nonce` for single-use nonce binding in Google One Tap callbacks.
migration_steps3 steps
01For generic OAuth, remove `Authorization` from `authorizationHeaders` and remove `authorization` from token-function `headers`; set the header using `customizeRequest` with `tokenEndpointAuth` method `custom`, including every provider-required credential.
02For manually invoking `/one-tap/callback` or `auth.api.oneTapCallback`, call `POST /one-tap/nonce`, pass the value to `google.accounts.id.initialize({ nonce })`, and send it as `nonce` in the callback body; remove client `nonce` and `additionalOptions.nonce` settings.
03For the built-in Kysely adapter, run `npx auth@latest migrate`. For Prisma or Drizzle, run `npx auth@latest generate` and apply the migration before deploying to add `expiresAt` to `oauthClient`; MongoDB requires no migration.
-SCIM provisioning of users and groups requires an adapter with native transactions; `/scim/v2` requests return 501 on adapters without them.
!SIWE verification no longer exposes internal error messages in 401 responses; details are logged server-side.
!SAML replay protection now rejects a signed response resubmitted with its assertion ID encoded as XML character references in the specified configurations.
!OAuth provider fixes revoke in-flight access tokens on adapters without foreign keys and return `invalid_grant` when reuse revokes an in-flight issuance.
+Cloudflare Workers are detected and reported as `workerd` by core telemetry, and runtime detection is exported from `@better-auth/core/env`.
+SCIM now handles groups with more than 100 members.
migration_steps3 steps
01For SCIM user and group provisioning, switch to an adapter with native transactions; adapters without them return 501 for `/scim/v2` requests.
02If relying on `update` to change every row matching a non-unique filter, use `updateMany` instead.
03If a MongoDB index build fails due to duplicate values, missing `createIndex` permission, or a conflicting index on the same field, fix the cause and restart.
Sign-up and update-user requests can no longer set `stripeCustomerId`; server code must set it through the database adapter instead.
!Fixed revoked sessions remaining usable with secondary storage or cookie caching, and added session-store checks to sensitive flows.
!Prevented unverified phone numbers and incorrectly verified OAuth email claims from being accepted; bound verification links and codes to the intended account.
!Fixed email OTP attempt limits under concurrent requests and tightened organization role, invitation, and trusted-origin checks.
!Fixed the Expo authorization proxy accepting server-unissued state or redirecting to unconfigured providers, and bound Electron authorization codes to the issuing browser session.
!Fixed passkey origin validation to use server configuration and enforced required user verification during registration and authentication.
migration_steps2 steps
01Add `set-phone` to custom access-control statements if they should permit `/admin/update-user` to change phone numbers.
02If server code sets `stripeCustomerId` through `auth.api.updateUser`, change it to write through the database adapter.