← Back
CVE-2026-53516
Authentication Bypass in better-auth (CVE-2026-53516)
Summary
authentication bypass in better-auth (CVE-2026-53516). Risk of unauthorized operations or information disclosure. Exploitable via ``next``. Mitigation: upgrade to `1.6.11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-53516** has been found in better-auth.
Attackers can target a specific entry point like ``next`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade better-auth to **1.6.11** or later.
If unsure, ask your IT team or search "better-auth CVE-2026-53516" on the vendor's site.
CVE-2026-53516 (better-auth) — CWE-287 /
Attack surface: `next` / `true` / `account.accountLinking.enabled` / `false`
Patched: `1.6.11` — apply immediately
Workaround: set account.accountLinking.enabled: 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
**authentication bypass** (CWE-287) exists in better-auth. Attackers reach the vulnerable code path via ``next`` without authentication.
📍 Affected scope
better-auth — . Attack surface: `next` / `true` / `account.accountLinking.enabled` / `false`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.6.11**.
🛡️ Workaround
Workaround: set account.accountLinking.enabled: false
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'better-auth' .` 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `better-auth` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set account.accountLinking.enabled: falseパッチが適用されるまでの応急処置として、set account.accountLinking.enabled: false を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade better-auth to 1.6.11ステージング環境で 1.6.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
better-auth
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.6.11"}]}]