Vulnerability in @better-auth/sso (CVE-2026-53513)
Summary
Vulnerability in @better-auth/sso (CVE-2026-53513). Confidential information can be exposed externally. Exploitable via POST /sso/register. Mitigation: upgrade to 1.6.11 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53513 has been found in @better-auth/sso.
Attackers can target a specific entry point like POST /sso/register over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade @better-auth/sso to 1.6.11 or later.
If unsure, ask your IT team or search "@better-auth/sso CVE-2026-53513" on the vendor's site.
CVE-2026-53513 (@better-auth/sso) — CWE-20 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /sso/register / POST /sso/update-provider / email / oidcConfig.userInfoEndpoint
Patched: 1.6.11 — apply immediately
Workaround: set trustEmailVerified: false
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in @better-auth/sso. Attackers reach the vulnerable code path via POST /sso/register.
Check the vendor advisory for the affected versions of @better-auth/sso. Attack surface: POST /sso/register / POST /sso/update-provider / email / oidcConfig.userInfoEndpoint.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 1.6.11.
Workaround: set trustEmailVerified: false
Search webserver/proxy logs for unusual POST /sso/register requests with malformed payloads or SQL meta-characters. Run grep -r '@better-auth/sso' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@better-auth/sso' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@better-auth/ssoを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /sso/register' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /sso/registerへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply temporary workaround mitigate
set trustEmailVerified: falseパッチが適用されるまでの応急処置として、set trustEmailVerified: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
4Apply patch patch
Upgrade @better-auth/sso to 1.6.11ステージング環境で 1.6.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
5Post-deployment verification verify
Replay attack against POST /sso/register on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com