dbcve.org
Better Auth\/ssoApplication · Better Auth

CVE-2026-53513

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 1.6.11 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Better Auth is an authentication and authorization library for TypeScript. Prior to 1.6.11, the @better-auth/sso plugin's POST /sso/register and POST /sso/update-provider endpoints accept attacker-controlled oidcConfig.userInfoEndpoint, tokenEndpoint, and jwksEndpoint URLs when skipDiscovery: true is set, store them on the ssoProvider row without origin validation, and fetch them during OIDC callback, allowing non-blind server-side request forgery and possible account linking when trustEmailVerified: true is configured. This issue is fixed in version 1.6.11.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The @better-auth/sso plugin allows attackers to supply arbitrary URLs for OIDC endpoints (userInfoEndpoint, tokenEndpoint, jwksEndpoint) via the /sso/register and /sso/update-provider endpoints when skipDiscovery: true is used. These URLs are stored without validation and fetched during OIDC callback, enabling non-blind SSRF attacks that can leak sensitive data or perform account linking when trustEmailVerified: true is configured.

MitigationUpgrade to better-auth version 1.6.11 or later. If unable to upgrade immediately, disable skipDiscovery: true and trustEmailVerified: true in SSO configurations as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Better Auth\/ssoApplication
Affected:< 1.6.11
Better AuthApplication
Affected:>= 0.1.0, < 1.6.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed better-auth version
    Run `npm list better-auth` or inspect your package.json dependencies to find the installed version
    Affected if The installed version is below 1.6.11 (e.g., 1.6.10, 1.6.0, 0.x.x)
  2. Identify if SSO plugin is in use
    Check your project for imports of @better-auth/sso and look for SSO provider configuration files or auth configuration that defines ssoProviders
    Affected if The @better-auth/sso plugin is installed and SSO providers are configured in your auth setup
  3. Check for skipDiscovery configuration in SSO providers
    Search your codebase for `skipDiscovery: true` within any SSO provider configuration (typically in a providers array for OIDC or similar)
    Affected if Any SSO provider has skipDiscovery set to true, allowing arbitrary URL injection
  4. Check for trustEmailVerified configuration
    Search your SSO or auth configuration for `trustEmailVerified: true` setting
    Affected if trustEmailVerified is set to true, which combined with the SSRF can enable sensitive data leakage or account linking attacks

Your environment is affected if better-auth version is below 1.6.11 AND you have SSO providers configured with skipDiscovery: true, regardless of trustEmailVerified setting.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.6.11 or later
Fixed in 1.6.11
Interim mitigation

Upgrade to better-auth version 1.6.11 or later. If unable to upgrade immediately, disable skipDiscovery: true and trustEmailVerified: true in SSO configurations as a temporary workaround.

Recommended fix High confidence

1.6.11

  1. Check current @better-auth/sso plugin version in package.json or package-lock.json
  2. Run 'npm install @better-auth/[email protected]' or 'npm update @better-auth/[email protected]' to upgrade to the fixed version
  3. Verify the upgrade completed successfully by checking the installed version with 'npm list @better-auth/sso'
  4. Test OIDC authentication flow to ensure the upgrade does not break existing functionality
  5. If using skipDiscovery: true, verify that the endpoints are now properly validated or that the fix addresses the SSRF vector

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Better Auth\/sso Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-53513 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data