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.
CVE-2026-53513
This critical-severity CVE scores 9.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.6
- EG Score
- 9.6(medium)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity96% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 16.2%
- KEV
- Not listed
Published
July 7, 2026
Last Modified
July 21, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026@better-auth/sso: Server-side request forgery via unvalidated OIDC endpoints on provider registration · Advisory · better-auth/better-auth · GitHub
https://github.com/better-auth/better-auth/security/advisories/GHSA-5rr4-8452-hf4vv1.6.11
Patch available: better-auth/better-auth v1.6.11
https://github.com/better-auth/better-auth/releases/tag/v1.6.11fix(sso): validate user-supplied OIDC endpoint URLs at registration and update
Fix merged in better-auth/better-auth PR #9574 on 2026-05-12 — awaiting tagged release
https://github.com/better-auth/better-auth/pull/9574commit 37f60cb176cb (better-auth/better-auth)
Fix landed in better-auth/better-auth commit 37f60cb176cb — awaiting tagged release
https://github.com/better-auth/better-auth/commit/37f60cb176cb53147da7dfd5ec15afa5b486e81eVendor Advisories for CVE-2026-53513(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| @better-auth/sso | — | 1.6.11 | — |
Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 03:19 UTCEG score recompute
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-07 21:13 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-20 · CWE-918
Frequently asked(5)
What is CVE-2026-53513?
When was CVE-2026-53513 disclosed?
Is CVE-2026-53513 actively exploited?
What is the CVSS score of CVE-2026-53513?
How do I remediate CVE-2026-53513?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53513
Is Your Infrastructure Affected by CVE-2026-53513?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.