Better Auth is an authentication and authorization library for TypeScript. From 1.2.10 until 1.6.11, the @better-auth/sso plugin's POST /sso/register endpoint lets any organization member attach a new SSO provider to that organization because registerSSOProvider checks only for a membership row and does not require an owner or admin role, allowing attacker-controlled OIDC or SAML providers to drive /sso/callback/{providerId} organization provisioning. This issue is fixed in version 1.6.11.
CVE-2026-53515
This high-severity CVE scores 7.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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
- 7.1
- EG Score
- 7.1(low)
- EPSS
- —
- KEV
- Not listed
Published
July 15, 2026
Last Modified
July 15, 2026
Advisory Details (4)
Auto-updated Jul 15, 2026@better-auth/sso: SSO provider may allow registration for any org member without a checking their role · Advisory · better-auth/better-auth · GitHub
https://github.com/better-auth/better-auth/security/advisories/GHSA-gv74-j8m3-fg5fv1.6.11
Patch available: better-auth/better-auth v1.6.11
https://github.com/better-auth/better-auth/releases/tag/v1.6.11fix(sso): require org admin role to register SSO providers
Fix merged in better-auth/better-auth PR #9220 on 2026-05-11 — awaiting tagged release
https://github.com/better-auth/better-auth/pull/9220commit 86765f159737 (better-auth/better-auth)
Fix landed in better-auth/better-auth commit 86765f159737 — awaiting tagged release
https://github.com/better-auth/better-auth/commit/86765f1597378f5c3deed1b80ca91faac0a6bf00Weakness Classification(3)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× 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-15 17:54 UTCEG score recompute
- 2026-07-15 17:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-269 · CWE-863
Frequently asked(4)
What is CVE-2026-53515?
When was CVE-2026-53515 disclosed?
What is the CVSS score of CVE-2026-53515?
How do I remediate CVE-2026-53515?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-53515
Is Your Infrastructure Affected by CVE-2026-53515?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.