CVE-2026-53513
SSRF and possible account linking via attacker-controlled OIDC endpoints in @better-auth/sso
Is CVE-2026-53513 being exploited?
Not confirmed. CVE-2026-53513 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-53513?
CVE-2026-53513 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-53513?
Yes. A fix has been recorded for CVE-2026-53513. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-53513 affect?
CVE-2026-53513 affects @better-auth/sso < 1.6.11, Better Auth (TypeScript) integrations, Node.js/TypeScript apps using @better-auth/sso with skipDiscovery:true. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-53513?
Upgrade to @better-auth/sso v1.6.11; validate OIDC endpoints and disable skipDiscovery
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Server-side request forgery via attacker-controlled OIDC endpoints; may enable account linking when trustEmailVerified=true.
Immediate action required
- affected>= 0.1.0 and < 1.6.11
- affected>= 0.1.0 and < 1.6.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.