# CVE-2026-114607: better-auth: OAuth state can be used as a Magic Link to sign in as another user


- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 23 Oct 2026

## What is CVE-2026-114607?

CVE-2026-114607 is a critical vulnerability in better-auth, published on 22 Oct 2026. 

### Official description

Better Auth is an authentication and authorization library for TypeScript. From 1.4.0-beta.18 until 1.7.7, deployments that enable Magic Link with storeToken set to plain, or with storeToken set to hashed and the global verification.storeIdentifier setting also set to hashed, enable a built-in social or Generic OAuth provider, and use account.storeStateStrategy set to database can accept an OAuth sign-in state value as a Magic Link token. These settings can cause Magic Link verification records and OAuth state to resolve to the same stored identifier, allowing an unauthenticated attacker to start OAuth sign-in for a known email address and redeem the returned state through Magic Link without controlling the mailbox or completing the provider callback. The attacker can obtain a normal session for an existing user, or create an account incorrectly marked as email verified when sign-up is enabled. This issue is fixed in version 1.7.7.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-114607?


## How do I fix CVE-2026-114607?

Upgrade to a fixed version.

## Is CVE-2026-114607 being exploited?

There is no known exploitation of CVE-2026-114607 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114607 and fix it if it is affected.

What it is: CVE-2026-114607 is a critical vulnerability in better-auth, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114607 in the wild and no public exploit code.

Affected product: better-auth. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114607/ (Markdown: https://insights.sbomify.com/CVE-2026-114607/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114607
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114607
- OSV: https://osv.dev/vulnerability/CVE-2026-114607

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114607/
Summaries are generated and may contain mistakes; the official description above is the record.