CVE-2026-53513
Better-auth Better Auth server-side request forgery (SSRF)
- Published15 Jul 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-53513 being actively exploited?
CVE-2026-53513 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.25%.
How severe is CVE-2026-53513?
CVE-2026-53513 has a CVSS 3.1 base score of 9.6, rated critical. EPSS estimates a 0.25% probability of exploitation.
Which products are affected by CVE-2026-53513?
Affected products include Better-auth Better Auth, Better-auth Better-auth/sso.
How do I fix CVE-2026-53513?
Upgrade affected software to a fixed version, for example Better-auth Better Auth 1.6.11, Better-auth Better-auth/sso 1.6.11 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-53513 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.