← Back
CVE-2026-53513
Vulnerability in @better-auth/sso (CVE-2026-53513)
Summary
vulnerability in @better-auth/sso (CVE-2026-53513). Risk of unauthorized operations or information disclosure. Exploitable via `POST /sso/register`. Mitigation: upgrade to `1.6.11` or later.
AI summary snake-internal / snake-material-v2
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.
Risk of unauthorized operations or information disclosure. CVSS score: ?/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 /
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.
❓ What is the problem
**A vulnerability** (CWE-20) exists in @better-auth/sso. Attackers reach the vulnerable code path via `POST /sso/register` without authentication.
📍 Affected scope
@better-auth/sso — . Attack surface: POST /sso/register / POST /sso/update-provider / `email` / `oidcConfig.userInfoEndpoint`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.6.11**.
🛡️ Workaround
Workaround: set trustEmailVerified: false
🔍 Detection
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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
3Hunt 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 があれば該当パスのアラート発火履歴を確認。
-
5Apply temporary workaround mitigate
set trustEmailVerified: falseパッチが適用されるまでの応急処置として、set trustEmailVerified: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade @better-auth/sso to 1.6.11ステージング環境で 1.6.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /sso/register on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
@better-auth/sso
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.11"}]}]