Sign in
Deutsch English Español Polski
High

Better Auth allows bypassing the trustedOrigins Protection which leads to ATO

  • Disclosed: 24.02.2025
  • Updated: 11.10.2026 10:22

Summary

A bypass was discovered in the trustedOrigins validation logic—affecting both absolute URL entries and wildcard domain patterns. This flaw allows an attacker to construct a malicious callbackURL that passes origin checks and triggers an open redirect.

Because redirect endpoints include sensitive tokens (such as password-reset tokens), this vulnerability can enable one-click account takeover if a victim clicks a crafted link.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package better-auth < 1.1.21 1.1.21

References

CVSS score 7.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
Weakness (CWE)
CWE-601
Platform
npm
Package
better-auth
Disclosed
24.02.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-vp58-j275-797x - CC BY 4.0

Vulnerability history: better-auth

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (22) in the archive
Total entries
22
First → latest
12.2024 07.2026
Without a fix
0
Exploited in attacks
0

Severity breakdown

  • Critical 2
  • High 14
  • Medium 3
  • Low 3

Disclosures per year

Severity:
  1. Better Auth: Account takeover via pre-account hijacking on magic-link and email-OTP sign-in
    High · 8.3 CVE-2026-67327 >= 1.1.3, < 1.6.22, >= 1.7.0-beta.0, < 1.7.0-beta.10 1.6.22, 1.7.0-beta.10
  2. @better-auth/oauth-provider's OAuth authorization-code grant allows concurrent redemption when two token requests race the find-then-delete primitive
    High · 8.1 CVE-2026-53518 < 1.6.11 1.6.11
  3. Better Auth: OAuth refresh-token rotation forks the token family on concurrent redemption
    High · 8.1 CVE-2026-53517 >= 1.4.8-beta.7, < 1.6.0 1.6.0
  4. Better Auth has insecure cryptographic defaults in oidcProvider: alg=none advertised and plain PKCE accepted by default
    High · 8.7 CVE-2026-67336 < 1.6.11 1.6.11
  5. Better Auth has stored XSS in the auth-server origin via javascript: redirect_uri in oidc-provider and mcp
    High · 7.7 CVE-2026-67333 < 1.6.13, >= 1.7.0-beta.0, < 1.7.0-beta.4 1.6.13, 1.7.0-beta.4
  6. Better Auth has an account takeover issue via OAuth auto-link to unverified pre-registered email
    High · 8.3 CVE-2026-53516 < 1.6.11 1.6.11
  7. Better Auth vulnerable to unauthorized invitation acceptance via unverified email match in organization plugin
    High · 7.7 CVE-2026-53514 < 1.6.11 1.6.11
  8. Better Auth: OAuth refresh-token replay via missing client authentication on oidc-provider and mcp plugins
    Critical · 9.1 CVE-2026-53512 < 1.6.11 1.6.11
  9. Better Auth: Device authorization approve and deny accept any authenticated session while the user code is pending
    High · 7.6 CVE-2026-45337 >= 1.6.0, < 1.6.11 1.6.11
  10. Better Auth: Rate limiter keys IPv6 addresses individually and is bypassable via prefix rotation
    High · 7.3 CVE-2026-45364 < 1.4.17, >= 1.5.0-beta.1, < 1.5.0-beta.9 1.4.17, 1.5.0-beta.9
  11. Better Auth Has Two-Factor Authentication Bypass via Premature Session Caching (session.cookieCache)
    Critical CVE-2026-67337 < 1.4.9 1.4.9
  12. Better Auth's rou3 Dependency has Double-Slash Path Normalization which can Bypass disabledPaths Config and Rate Limits
    High · 8.6 CVE-2025-71399 < 1.4.5 1.4.5
  13. Better Auth affected by external request basePath modification DoS
    High CVE-2025-71401 < 1.4.2 1.4.2
  14. Better Auth: Unauthenticated API key creation through api-key plugin
    High · 8.6 CVE-2025-61928 < 1.3.26 1.3.26
  15. Better Auth allows bypassing the trustedOrigins Protection which leads to ATO this entry
    High · 7.1 CVE-2025-71403 < 1.1.21 1.1.21
  16. Better Auth has an Open Redirect Vulnerability in Verify Email Endpoint
    High CVE-2024-56734 < 1.1.6 1.1.6

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Privacy policy

Free to subscribe. Unsubscribe with one click in any email.