Google One Tap no longer authenticates wrong user; stale session cookies fixed
v1.6.14
6 fixesThis release6 fixesBug fixesAI-tallied from the release notes
better-auth
Bug Fixes
- Fixed Google One Tap authenticating the wrong user when the presented Google account was already linked to a different local user.
- Fixed
nullvalues being rejected for optional fields in the generated database schema (#9841) - Fixed
getSessionCookieto prefer the__Secure-prefixed cookie over a non-secure leftover, preventing a stale cookie from shadowing the current session (#9806) - Fixed redirect URI validation to work on all supported runtimes and to reject URIs containing a fragment component per RFC 6749 §3.1.2 (#9845)
- Fixed organization invitation verification to restore the normal emailed-invitation flow while enforcing stricter email verification for externally controlled or predictable invitation IDs (#9877)
For detailed changes, see CHANGELOG
@better-auth/sso
Bug Fixes
- Fixed SAML Single Logout leaving the user signed in due to the logout handlers matching the session by ID instead of token.
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
Full changelog: v1.6.13...v1.6.14
Fetched June 2, 2026

