Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA GitHub_M

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

CriticalCVSS 9.1 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 36/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: better-auth better-auth 1.7.7.

Low priority for now. Upgrade to better-auth better-auth 1.7.7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Oct 22, 2026
Updated
Oct 23, 2026
EPSS
0.4% · 36th percentile

Report tools

JSON

Action score

36

Monitor

Low priority for now.

CVSS
36 / 40 · 9.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-114607

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for better-auth records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • better-auth better-auth

    • >= 1.4.0-beta.18, < 1.7.7affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmbetter-authfrom 1.4.0-beta.18 · before 1.7.71.7.7

Same product

better-auth: all records

Other highest-scoring records for the same primary product.

  • CVE-2025-61928Better Auth: Unauthenticated API key creation through api-key plugin
    43Plan
  • CVE-2026-110862Better Auth 1.4.0-beta.18 before 1.7.7 Authentication Bypass via Magic Link
    37Monitor
  • CVE-2025-71401better-auth before 1.4.2 basePath Modification DoS
    37Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-71399Aug 2, 2026 · Better Auth before 1.4.5 Path Normalization Bypass via rou3
    35Monitor
  • ← EarlierCVE-2026-109346Oct 12, 2026 · better-auth 1.3.8-beta.3 before 1.7.0-rc.3 Device Authorization Phishing via /device
    34Monitor
  • ← EarlierCVE-2026-110864Oct 14, 2026 · Better Auth 1.5.0-beta.12 before 1.7.7 Authentication Bypass via OAuth Proxy
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
better-auth better-auth1.7.7 · descriptionVendor (CNA)
npm:better-auth1.7.7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 13, 2026+22 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-1108628 days apartBetter Auth 1.4.0-beta.18 before 1.7.7 Authentication Bypass via Magic Link
    37Monitor
  • CVE-2026-1108648 days apartBetter Auth 1.5.0-beta.12 before 1.7.7 Authentication Bypass via OAuth Proxy
    36Monitor
  • CVE-2026-6732782 days apartbetter-auth before 1.6.22 Account Takeover via Magic-Link Email-OTP
    34Monitor
  • CVE-2026-6733582 days apartbetter-auth before 1.6.2 OAuth State Validation Bypass
    24Monitor

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Not on record for this CVE: researcher credit.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

nvd-secondary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. SSVC exploitation— → none
  2. Exploit maturity— → none
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records