cve.bz

CVE-2026-53513 better-auth: Confused Deputy

9.6 criticalEPSS 0.2%Fix available

Critical (9.6) in better-auth. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @better-auth/sso 1.6.11.

On this page
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.

Severity

CVSS 3.1

9.6 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-345 Insufficient Verification of Data Authenticity
CWE-441 Unintended Proxy or Intermediary (Confused Deputy)
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53513 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53513?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53513?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53513 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
better-auth:better-auth/ssobefore 1.6.11
better-auth:better_authfrom 0.1.0 before 1.6.11

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-5rr4-8452-hf4vnpm@better-auth/sso>=0.1.0 <1.6.111.6.11

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High
  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-465 Transparent Proxy Abuse Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12), CWE-20 (51).

References

Check your stackJSON